You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this gem (re)defines APP_PATH, we get the following warning when starting rails. /usr/local/bundle/bundler/gems/standalone-migrations-51197b69f14d/lib/standalone_migrations.rb:13: warning: already initialized constant APP_PATH bin/rails:2: warning: previous definition of APP_PATH was here
We were ignoring this until we realised that it caused issues with other gems (in particular doorkeeper) which assumed a different APP_PATH while generating files.
We were able to work around it by commenting it out temporarily, but is there a better way to fix this? Any suggestions? Would be happy to raise a PR if we can.
The text was updated successfully, but these errors were encountered:
I'm not sure about this, but isn't the standalone_migration gem made to be able to use active_record migrations and commands without rails?
EDIT: Yes it is: Rails migrations in non-Rails (and non Ruby) projects.
Is there a reason for you to use the gem in a Rails project, then? If not, it would be best for you to just remove the dependency to the standalone_migration gem and let Rails do everything :)
Since this gem (re)defines APP_PATH, we get the following warning when starting rails.
/usr/local/bundle/bundler/gems/standalone-migrations-51197b69f14d/lib/standalone_migrations.rb:13: warning: already initialized constant APP_PATH bin/rails:2: warning: previous definition of APP_PATH was here
We were ignoring this until we realised that it caused issues with other gems (in particular doorkeeper) which assumed a different APP_PATH while generating files.
We were able to work around it by commenting it out temporarily, but is there a better way to fix this? Any suggestions? Would be happy to raise a PR if we can.
The text was updated successfully, but these errors were encountered: