postgresql-migrations
bytebase
| postgresql-migrations | bytebase | |
|---|---|---|
| 1 | 36 | |
| 46 | 10,029 | |
| - | 2.1% | |
| 10.0 | 10.0 | |
| over 4 years ago | 7 days ago | |
| PLpgSQL | 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.
postgresql-migrations
-
What migration/versioning tool do you use?
I wrote my own simple solution, and I (and some others) have used it with some success in a few commercial projects. https://github.com/purcell/postgresql-migrations
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?
alembic - A database migrations tool for SQLAlchemy.
liquibase - Main Liquibase Source
tern - The SQL Fan's Migrator
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
goose - A database migration tool. Supports SQL migrations and Go functions.
migra - Like diff but for PostgreSQL schemas
jaeger-clickhouse - Jaeger ClickHouse storage plugin implementation
sqldef - Idempotent schema management for MySQL, PostgreSQL, and more
gorm-seeder - Gorm seeder package
profanity - Ncurses based XMPP client
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes 🚀