[openstreetmap/openstreetmap-website] Use strong_migrations (#2237)

[Andy Allan]

… to help developers avoid problems in production database schema changes.

I've used this gem in other projects and I find it really useful. For many developers it's not clear which migrations can be done near-instantly (e.g. adding a new column) and which migrations will lock a table, potentially for hours (e.g. adding a new column with a default value).

This gem highlights bad migrations during development, so that the developers can learn what the problems might be before the sysadmins find out in production. I've set it to ignore all existing migrations since some of them won't have been safe, but that no longer matters.
You can view, comment on, or merge this pull request online at:

  https://github.com/openstreetmap/openstreetmap-website/pull/2237

-- Commit Summary --

  * Use strong_migrations to help developers avoid problems in production database schema changes

-- File Changes --

    M Gemfile (1)
    M Gemfile.lock (3)
    A config/initializers/strong_migrations.rb (1)

-- Patch Links --

https://github.com/openstreetmap/openstreetmap-website/pull/2237.patch
https://github.com/openstreetmap/openstreetmap-website/pull/2237.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/2237
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190529/d0103157/attachment-0001.html>