Although this thread started to me from the single bug (unexpected "feature") I want to address the issue more widely.
There is a methodology (approach) to develop portable, scalable and maintainable web-services called "The Twelve-Factor App". On of it's "factors" is the environment agnostic approach to configuration (although it is not called so explicitly in the document, I think this two words expresses the sense): http://12factor.net/config It is almost possible to be environment agnostic with Rails. But there are some issues. The issue I mentioned is this: https://github.com/rails/rails/blob/3ba176d0a07728e9505609967b518d85129bff24/activerecord/lib/active_record/tasks/database_tasks.rb#L282 And here is some consequences: https://github.com/laserlemon/figaro/issues/225 Rails tries to be in two environments in a single run. It looks bad. It's surprising. It prevents effective environment management (homogeneous config applicable to any environment). What do you about environment agnostic approach and about it implicit support by Rails (e.g. everything works if you doesn't mention any environment enywhere in your project)? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
