nandi
migration_signature
| nandi | migration_signature | |
|---|---|---|
| 1 | 1 | |
| 124 | 4 | |
| 0.0% | - | |
| 5.1 | 4.4 | |
| 4 months ago | 4 months ago | |
| Ruby | Ruby | |
| 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.
nandi
-
Show HN: Zero-downtime PostgreSQL migrations for Ruby on Rails
We have something similar https://github.com/gocardless/nandi
It does signature checking and some and some other helpful things.
migration_signature
-
Show HN: Zero-downtime PostgreSQL migrations for Ruby on Rails
This is cool. We use strong_migrations but I’ll check this out. I love the idea of an enforced pattern for background data migrations.
While I’m here a shameless plug for a gem we built that we’ve found incredibly helpful for safer migrations - https://github.com/TandaHQ/migration_signature
It adds a CI check to guarantee the migrations you tested in development are actually the migrations that run in production.
What are some alternatives?
django-pg-zero-downtime-migrations - Django postgresql backend that apply migrations with respect to database locks
safe-pg-migrations - Make your PostgreSQL migrations safe
pg-osc - Easy CLI tool for making zero downtime schema changes and backfills in PostgreSQL
django-zerodowntime - django migration utilities for zero downtime continuous delivery
django-check-migration-wtf - check migrations of django to work on enviroment zero downtime
online_migrations - Catch unsafe PostgreSQL migrations in development and run them easier in production (code helpers for table/column renaming, changing column type, adding columns with default, background migrations, etc).