strong_migrations
lockbox
Our great sponsors
strong_migrations | lockbox | |
---|---|---|
16 | 13 | |
3,797 | 1,369 | |
- | - | |
7.7 | 7.5 | |
7 days ago | about 1 month 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
-
Must-have gems for mature Rails
gem "strong_migrations" - https://github.com/ankane/strong_migrations | Helps devs write non-blocking migrations, a must-have.
-
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.
-
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.
-
Database... or Goose?
Nice one! Personally, I've been using https://github.com/ankane/strong_migrations to cover this case.
-
Ten Ruby gems for Rails you should definitely know about
StrongMigrations
-
Elixir and Phoenix after two years
> Ecto prevents N+1 queries by default, which I think is clearly better.
To be fair...
If you want to protect yourself from these with Rails you can install Bullet[0] and get protection through in your face notifications, and you have the option to let it slide because you're taking advantage of caching with Rails and in this case you know what you're getting into and the N+1 query with caching ends up being better because you understand your domain.
Rails also has the strong migrations[1] gem which is a huge help for not shooting yourself in the foot for running migrations in production by helping you avoid table locks and other issues / errors. But AFAIK there's no Ecto equivalent, but strong migrations is really really useful.
Rails also has the data-migrate gem which is a nice little abstraction for splitting out your schema changes and backfilling data in an automated way. There's nothing like with Ecto. This one isn't as useful as strong migrations IMO but it's still very handy to have this problem taken care of for you without having to re-invent a new strategy in every project or copy code over.
Basically all 3 of these things are something I'd use in every project in Rails but with Phoenix I wouldn't have these things except for N+1 query protection.
[0]: https://github.com/flyerhzm/bullet
lockbox
-
Advanced Usages of Devise for Rails
The first step is to install the gem with bundle add authtrail. Additionally, since you'll be storing user-identifiable information such as emails and IP addresses in your app database, it's highly recommended that you encrypt this data in production using a combination of Lockbox and Blindindex gems.
-
Searching/Querying with Active Record Encryption
It allowed us to implement a partial search inside fields that are encrypted using lockbox (https://github.com/ankane/lockbox)
Your app queries an encrypted ActiveStash index, which says what rows in your existing database should be retrieved. It works with all the popular application-level encryption plugins for ActiveRecord, including ActiveRecord Encryption, and Lockbox.
-
Life monitoring with org mode and telegram chat bot
Content is encrypted using https://github.com/ankane/lockbox default setup I've been considering adding optional end-to-end encryption as well, but am a bit afraid people might lose access to content forever if they lose access to keys.
-
Rails application boilerplate for fast MVP development
lockbox and blind_index for email fields encryption
-
Build an API in Rails with Authentication
Install lockbox and blind_index.
-
Question on encrypted content
https://github.com/ankane/lockbox this is for the actual encryption of data
- DB Encryption
-
Ten Ruby gems for Rails you should definitely know about
Lockbox
-
Rails 7 introduces Active Record Encryption
I've been using the lockbox gem to encrypt specified attributes.
What are some alternatives?
safe-pg-migrations - Make your PostgreSQL migrations safe
attr_encrypted - Generates attr_accessors that encrypt and decrypt attributes
blind_index - Securely search encrypted database fields
phony_rails - This Gem adds useful methods to your Rails app to validate, display and save phone numbers. It uses the super awesome Phony gem (https://github.com/floere/phony).
money-rails - Integration of RubyMoney - Money with Rails
rails_best_practices - a code metric tool for rails projects
data-migrate - Migrate and update data alongside your database structure.
Pagy - 🏆 The Best Pagination Ruby Gem 🥇
ghost_adapter - Run ActiveRecord migrations through gh-ost
Large Hadron Migrator - Online MySQL schema migrations
indifferent_access - [ALPHA] - Elixir Plug/Utility doing questionable things with maps/params