sqitch
smoothdb
sqitch | smoothdb | |
---|---|---|
7 | 2 | |
2,715 | 17 | |
1.2% | - | |
7.2 | 9.2 | |
about 2 months ago | 10 days ago | |
Perl | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sqitch
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
We use https://sqitch.org/ and we’re fairly happy with it. Sqitch manages the files to deploy which are applied fits to a local database.
We use GitHub actions for deployment and database migrations are just one step of the pipeline. The step invokes sqitch deploy which runs all the pending migration files.
Then, all the approval process is standard for the environment. We require approvals in pull requests before merging to the main branch.
-
PostgREST: Providing HTML Content Using Htmx
I'm experimenting with it right now using Squitch [1] to make maintenance easier. It still feels like a hack and I also still have my doubts about the viability of this for real-world use. It's fun though and I'm learning about all kinds of advanced Postgres features.
[1] https://sqitch.org/
-
Modern Perl Catalyst: Docker Setup
For developing I find the official Perl docker images, running on a lightweight version of Debian, to be perfectly fine. Later on you might hand roll the skinniest possible image but the beauty of this setup is you can do that later and you don't need to change anything else. There's really not a lot going on here. First I declare the base image, which is as I said the official Perl image. I'm not using the latest Perl here because the application uses Sqitch for managing database migrations and that needs an update (there's a PR pending) to run on the most recent Perl so we'll just use a very nearly recent one instead. WORKDIR just defines where your application is installed. You can put it anywhere you want within reason. I like simple things so I use the most simple of all the conventions I've seen around.
-
Database migration tool
Also, https://sqitch.org/
- How do you handle schema migrations?
-
Announcing codd - a tool to apply postgres SQL migrations
Some possible upsides of codd: - No need to manually write verification SQL. Codd will update schema representation files when you codd add some-migration.sql and will compare those to the actual schema when deploying (I'd say in ways which would be very hard to replicate manually, see an example of what codd checks, giving you the option to rollback if they don't match or proceed but log non-matching db objects. - It seems to be much simpler to set codd up. You need 3 env vars to start, a folder to store your migrations and a self-contained statically linked executable. Just codd add migration.sql your way in after that - This might be very wrong as I couldn't find it explicitly documented, but this GH issue suggests it's not so simple to apply all pending migrations in a single transaction with Sqitch? Maybe it requires some bundling or something along those lines and then it's fine, though. In any case, codd will do this automatically when you run codd up (provided postgresql allows it).
smoothdb
-
Pocketbase: Open-source back end in 1 file
Pocketbase seems really well done and useful.
I am building something similar but at a lower level and based on PostgreSQL.
https://github.com/sted/smoothdb
It aims to be compatible with the PostgREST API.
-
PostgREST: Providing HTML Content Using Htmx
For those who might be interested, I've recently published SmoothDB on GitHub [1], which, like PostgREST, provides a RESTful API to PostgreSQL databases.
It's a beta, aiming for compatibility with PostgREST, but it's not ready for production yet (so continue to use the very good PostgREST).
Written in Go, SmoothDB can be used both stand-alone and as a module for more complex server applications, which was my main motivation for writing this.
Your thoughts and contributions are greatly appreciated as they will help in the ongoing development and refinement of SmoothDB.
[1] https://github.com/sted/smoothdb
What are some alternatives?
ContactsDemo - Example Catalyst Application
couchapp - Utilities to make standalone CouchDB application development simple
migrate - Database migrations. CLI and Golang library.
pocketbase-nuxt - A test project with pocketbase
atlas - Manage your database schema as code
plmustache - Logic-less templates for Postgres
maildev - :mailbox: SMTP Server + Web Interface for viewing and testing emails during development.
neurelo-go-htmx-example - A go project built using Neurelo and Htmx.
git-secret - :busts_in_silhouette: A bash-tool to store your private data inside a git repository.
docker-pocketbase - miguelgargallo/docker-pocketbase
docs - Documentation for Docker Official Images in docker-library
pocketbase - PocketBase client SDK for python