lockbox VS strong_migrations

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.

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.

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.

lockbox and blind_index for email fields encryption

Install lockbox and blind_index.

https://github.com/ankane/lockbox this is for the actual encryption of data

Lockbox

I've been using the lockbox gem to encrypt specified attributes.

I stumbled upon lockbox when looking for alternatives to attr_encrypted (It hadn't been updated for a while). It's really super & I'm pretty keen to share it :D

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.

gem "strong_migrations" - https://github.com/ankane/strong_migrations | Helps devs write non-blocking migrations, a must-have.

Frameworks will have a preferred solution. We use Rails with the strong_migrations gem which is great: https://github.com/ankane/strong_migrations

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.

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.

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.

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