strong_migrations
phony_rails
Our great sponsors
strong_migrations | phony_rails | |
---|---|---|
17 | 1 | |
3,856 | 547 | |
- | - | |
8.1 | 0.0 | |
29 days ago | about 1 year 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.
strong_migrations
-
Careful with That Lock, Eugene
In the Rails world, the gem strong_migrations can be used to detect these: https://github.com/ankane/strong_migrations
The docs include a handy articulation of fixes.
-
Must-have gems for mature Rails
gem "strong_migrations" - https://github.com/ankane/strong_migrations | Helps devs write non-blocking migrations, a must-have.
-
Migration Best Practice
Frameworks will have a preferred solution. We use Rails with the strong_migrations gem which is great: https://github.com/ankane/strong_migrations
-
How does Rails handle out of order migrations (when working on different local branches)
There’s no real way to test, but you can use gems like https://github.com/ankane/strong_migrations and not allow to merge branches unless they are up-to-date with main.
-
[AskJS] Is there any alternative to the strong migrations gem?
The strong migrations gem in Rails alerts when you're trying to make a migration that may be dangerous. Does anyone know an alternative for Javascript? Or maybe for raw SQL.
- Adding first and last name to existing app running on Heroku
- Enforcing Zero Downtime Django Migrations
-
When Postgres blocks: tips for dealing with locks
Half of the problems in this article are migration related.
I am extremely grateful that some people have created awesome libraries like strong migrations https://github.com/ankane/strong_migrations. Even if you are not using rails, bookmark its readme, it is an awesome cheat-sheet when writing a migration.
- Best practices as code using RuboCop
-
Why I Enjoy PostgreSQL – Infrastructure Engineer's Perspective
I would suggest taking a look at strong migrations[1]. It's a rails project, but the readme does a great job explaining what it checks for and what safe alternative to use instead. I still link to their explanations in PRs for non-rails projects.
[1]: https://github.com/ankane/strong_migrations#checks
phony_rails
What are some alternatives?
safe-pg-migrations - Make your PostgreSQL migrations safe
Pagy - 🏆 The Best Pagination Ruby Gem 🥇
money-rails - Integration of RubyMoney - Money with Rails
lockbox - Modern encryption for Ruby and Rails
Light Service - Series of Actions with an emphasis on simplicity.
data-migrate - Migrate and update data alongside your database structure.
Kaminari - ⚡ A Scope & Engine based, clean, powerful, customizable and sophisticated paginator for Ruby webapps
counter_culture - Turbo-charged counter caches for your Rails app.
ghost_adapter - Run ActiveRecord migrations through gh-ost