gitlab-org--gitlab-foss/config/initializers/0_migration_paths_additional.rb

# frozen_string_literal: true

# Because we use Gitlab::Database, which in turn uses prepend_mod_with,
# we need this intializer to be after config/initializers/0_inject_enterprise_edition_module.rb.

# Post deployment migrations are included by default. This file must be loaded
# before other initializers as Rails may otherwise memoize a list of migrations
# excluding the post deployment migrations.
Gitlab::Database.add_post_migrate_path_to_rails
Add latest changes from gitlab-org/gitlab@master 2021-02-03 16:09:17 -05:00			`# frozen_string_literal: true`

Add latest changes from gitlab-org/gitlab@master 2021-06-28 17:10:13 -04:00			`# Because we use Gitlab::Database, which in turn uses prepend_mod_with,`
			`# we need this intializer to be after config/initializers/0_inject_enterprise_edition_module.rb.`

Support for post deployment migrations These are regular Rails migrations that are executed by default. A user can opt-out of these migrations by setting an environment variable during the deployment process. Fixes gitlab-org/gitlab-ce#22133 2016-10-27 08:36:53 -04:00			`# Post deployment migrations are included by default. This file must be loaded`
			`# before other initializers as Rails may otherwise memoize a list of migrations`
			`# excluding the post deployment migrations.`
Ensure the schema is loaded with post_migrations included If doing a schema load, the post_migrations should also be marked as up, even if SKIP_POST_DEPLOYMENT_MIGRATIONS was set, otherwise future migration runs will be broken. 2018-09-11 21:41:14 -04:00			`Gitlab::Database.add_post_migrate_path_to_rails`