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

This commit is contained in:
Andy Allan 2019-05-29 11:05:09 +02:00
parent ea68ac865b
commit 3e414a5025
3 changed files with 5 additions and 0 deletions

View file

@ -61,6 +61,7 @@ gem "rack-cors"
gem "rails-i18n", "~> 4.0.0"
gem "record_tag_helper"
gem "rinku", ">= 2.0.6", :require => "rails_rinku"
gem "strong_migrations"
gem "validates_email_format_of", ">= 1.5.1"
# Native OSM extensions

View file

@ -405,6 +405,8 @@ GEM
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
strong_migrations (0.3.1)
activerecord (>= 3.2.0)
term-ansicolor (1.7.1)
tins (~> 1.0)
terrapin (0.6.0)
@ -510,6 +512,7 @@ DEPENDENCIES
sanitize
sassc-rails
secure_headers
strong_migrations
therubyracer
uglifier (>= 1.3.0)
validates_email_format_of (>= 1.5.1)

View file

@ -0,0 +1 @@
StrongMigrations.start_after = 20190518115041 # rubocop:disable Style/NumericLiterals