discourse/config/initializers/000-post_migration.rb

# frozen_string_literal: true

unless Discourse.skip_post_deployment_migrations?
  ActiveRecord::Tasks::DatabaseTasks.migrations_paths << Rails.root.join(
    Discourse::DB_POST_MIGRATE_PATH
  ).to_s
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-02 17:17:27 -05:00			`# frozen_string_literal: true`

DEV: Support post deployment migrations for plugins. 2018-10-09 00:11:45 -05:00			`unless Discourse.skip_post_deployment_migrations?`
FIX: Migration paths were being forgotten According to the [Rails Source](https://github.com/rails/rails/blob/master/activerecord/lib/active_record/railties/databases.rake#L20) the `ActiveRecord::Migrator.migrations_paths` are overwritten with the value of `ActiveRecord::Tasks::DatabaseTasks.migrations_paths` every time the config is loaded. This caused a bug for Discourse development where if you ran: `rake db:drop db:create db:migrate` in one line, you would not get our post migrations, as those had a custom value for `migrations_paths`. The fix is to use `ActiveRecord::Tasks::DatabaseTasks.migrations_paths` to set up all our custom paths. Everything seems to work as expected. 2019-12-16 13:11:55 -06:00			`ActiveRecord::Tasks::DatabaseTasks.migrations_paths << Rails.root.join(`
FEATURE: Post deployment migrations. (#6406) This moves us away from the delayed drops pattern which was problematic on two counts. First, it uses a hardcoded "delay for" duration which may be too short for certain deployment strategies. Second, delayed drop doesn't ensure that it only runs after the latest application code has been deployed. If the migration runs and the application code fails to deploy, running the migration after "delay for" has been met will cause the application to blow up. The new strategy allows post deployment migrations to be skipped if the env `SKIP_POST_DEPLOYMENT_MIGRATIONS` is provided. ``` SKIP_POST_DEPLOYMENT_MIGRATIONS=1 rake db:migrate -> deploy app servers SKIP_POST_DEPLOYMENT_MIGRATIONS=0 rake db:migrate ``` To aid with the generation of a post deployment migration, a generator has been added. Simply run `rails generate post_migration`. 2018-10-08 02:47:38 -05:00			`Discourse::DB_POST_MIGRATE_PATH`
			`).to_s`
			`end`