kevinsivic/dawarich
1
0
Fork 0
mirror of https://github.com/Freika/dawarich.git synced 2026-01-10 01:01:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Remove strong_migrations gem for now

Browse source
This commit is contained in:
Eugene Burmakin 2025-11-07 20:18:56 +01:00
parent b272c7407f
commit f48a512b10
3 changed files with 23 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Gemfile
View file

@ -48,7 +48,7 @@ gem 'sidekiq-limit_fetch'
gem 'sprockets-rails'
gem 'stackprof'
gem 'stimulus-rails'
gem 'strong_migrations', '>= 2.4.0'
# gem 'strong_migrations', '>= 2.4.0'
gem 'tailwindcss-rails', '= 3.3.2'
gem 'turbo-rails', '>= 2.0.17'
gem 'tzinfo-data', platforms: %i[mingw mswin x64_mingw jruby]

3
Gemfile.lock
View file

@ -486,8 +486,6 @@ GEM
stimulus-rails (1.3.4)
railties (>= 6.0.0)
stringio (3.1.7)
strong_migrations (2.5.1)
activerecord (>= 7.1)
super_diff (0.17.0)
attr_extras (>= 6.2.4)
diff-lcs
@ -600,7 +598,6 @@ DEPENDENCIES
sprockets-rails
stackprof
stimulus-rails
strong_migrations (>= 2.4.0)
super_diff
tailwindcss-rails (= 3.3.2)
turbo-rails (>= 2.0.17)

44
config/initializers/strong_migrations.rb
View file

@ -1,27 +1,27 @@
# Mark existing migrations as safe
StrongMigrations.start_after = 20_250_122_150_500
# # Mark existing migrations as safe
# StrongMigrations.start_after = 20_250_122_150_500
# Set timeouts for migrations
# PgBouncer in transaction mode doesn't support SET commands
# Timeouts should be set on the database user instead
# StrongMigrations.lock_timeout = 10.seconds
# StrongMigrations.statement_timeout = 1.hour
# # Set timeouts for migrations
# # PgBouncer in transaction mode doesn't support SET commands
# # Timeouts should be set on the database user instead
# # StrongMigrations.lock_timeout = 10.seconds
# # StrongMigrations.statement_timeout = 1.hour
# Analyze tables after indexes are added
# Outdated statistics can sometimes hurt performance
StrongMigrations.auto_analyze = true
# # Analyze tables after indexes are added
# # Outdated statistics can sometimes hurt performance
# StrongMigrations.auto_analyze = true
# Set the version of the production database
# so the right checks are run in development
# StrongMigrations.target_version = 10
# # Set the version of the production database
# # so the right checks are run in development
# # StrongMigrations.target_version = 10
# Add custom checks
# StrongMigrations.add_check do |method, args|
# if method == :add_index && args[0].to_s == "users"
# stop! "No more indexes on the users table"
# end
# end
# # Add custom checks
# # StrongMigrations.add_check do |method, args|
# # if method == :add_index && args[0].to_s == "users"
# # stop! "No more indexes on the users table"
# # end
# # end
# Make some operations safe by default
# See https://github.com/ankane/strong_migrations#safe-by-default
# StrongMigrations.safe_by_default = true
# # Make some operations safe by default
# # See https://github.com/ankane/strong_migrations#safe-by-default
# # StrongMigrations.safe_by_default = true