sqitch
bytebase
sqitch | bytebase | |
---|---|---|
7 | 36 | |
2,715 | 10,161 | |
1.2% | 3.4% | |
7.2 | 10.0 | |
about 2 months ago | 1 day ago | |
Perl | Go | |
MIT License | GNU General Public License v3.0 or later |
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).
bytebase
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
We have been building https://github.com/bytebase/bytebase for 3+ years. You can think it of as GitHub/GitLab for SQL changes, with integrated GitOps, code review and deployment.
You can further check out this tutorial to get a feel of our GitOps solution
https://www.bytebase.com/docs/tutorials/database-change-mana...
-
Resend – Incident report for February 21st, 2024
We have been working on bytebase (https://github.com/bytebase/bytebase) for 3+ years to address this. With a change review workflow, environment propagations, and try not to disturb the dev flow if possible.
-
PostgreSQL Is Enough
Migrations. All my database logic lives in version control.
Popular tooling like Phoenix, Hasura, etc have good built in migration stories.
https://www.bytebase.com looks really promising.
Hover, I do struggle with one big issue: changing database logic (views, functions, etc) that has other logic dependent on it. This seems like a solvable problem.
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
bytebase.com — Database CI/CD and DevOps. Free under 20 users and ten database instances
-
🚛 Deploy Database Schema Migrations with Bytebase
Bytebase offers a powerful GUI for schema migration deployments. This tutorial will show you how to use Bytebase to deploy schema migrations with features like SQL Review, custom approval, time scheduling, and more.
- Bytebase – The Only Database CI/CD Workspace
-
Are "Infrastructure as Code" limited to "Infrastructure" only?
Now there are more subdivided practice: * Policy as Code: Sentinel, OPA * Database as Code: bytebase * AppConfiguration as Code: KusionStack, Acorn * ...... (Welcome to add more)
-
🐬Top 5 MySQL GUI Clients to Command MySQL⚡️
Bytebase is an open-source Database DevOps and CI/CD tool for teams, designed to centralize the control and secure your organization’s most valuable asset, the database data.
-
database changes tracking tools
I use Bytebase to manage database changes for MySQL with GitOps workflow. I can manage my SQL scripts in my GitLab repo, and trigger a database change issue with committing a MR. Then Bytebase will record it after the issue is executed successfully. But I am not sure whether it supports procedures. Refer to https://github.com/bytebase/bytebase to get more details.
- Version control for database used by C# app
What are some alternatives?
ContactsDemo - Example Catalyst Application
liquibase - Main Liquibase Source
migrate - Database migrations. CLI and Golang library.
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
atlas - Manage your database schema as code
migra - Like diff but for PostgreSQL schemas
maildev - :mailbox: SMTP Server + Web Interface for viewing and testing emails during development.
jaeger-clickhouse - Jaeger ClickHouse storage plugin implementation
git-secret - :busts_in_silhouette: A bash-tool to store your private data inside a git repository.
sqldef - Idempotent schema management for MySQL, PostgreSQL, and more
docs - Documentation for Docker Official Images in docker-library
alembic - A database migrations tool for SQLAlchemy.