22c1c9805b
It could happen that there's a cached (in Redis) ApplicationSetting record, and calling `Gitlab::CurrentSettings.current_application_settings` only returns it instead of creating a new DB record, which makes the `ApplicationSetting.current_without_cache.update!` call fail. Signed-off-by: Rémy Coutable <remy@rymai.me>
10 lines
361 B
Ruby
10 lines
361 B
Ruby
# frozen_string_literal: true
|
|
|
|
puts "Creating the default ApplicationSetting record.".color(:green)
|
|
ApplicationSetting.create_from_defaults
|
|
|
|
# Details https://gitlab.com/gitlab-org/gitlab-ce/issues/46241
|
|
puts "Enable hashed storage for every new projects.".color(:green)
|
|
ApplicationSetting.current_without_cache.update!(hashed_storage_enabled: true)
|
|
|
|
print '.'
|