I highly recommend against "custom" environments. I disagree with using environments for configuration (such as database connections), they should be used for behavior.
Here's a thing I wrote about the problems you can get into by solving problems by creating new "env" types: https://devcenter.heroku.com/articles/deploying-to-a-custom-rails-environment While i'm talking about "staging" as an env, I think it's generally applicable to any non development/production/test environments. I also don't think the problem you're trying to solve with a custom environment is fully formed. I've not found a need for a custom test like environment. -- Richard Schneeman http://schneems.com On March 1, 2017 at 7:36:22 AM, Chad Woolley (thewoolley...@gmail.com) wrote: See also this thread: https://groups.google.com/d/topic/rubyonrails-core/kqKoJHcQu9U/discussion ...wherein is discussed (without any official response from core contributors) many of the warts and limitations of RAILS_ENV in a modern, cloud-native-y, 12-factor-y world. -- Chad On Mon, Feb 27, 2017 at 6:15 AM, Vijay Raghavan Aravamudhan <avij...@gmail.com> wrote: With the latest merge into the master branch of this https://github.com/rails/rails/pull/26703, it seems that the core framework is heading in a direction where functional/system tests are also being accepted in a more formal way. If this is the case, imo, it would make sense to also have a RAILS_ENV that is separate from the ubiquitous 'test' env. In all my RoR projects where we have written automated functional tests using some framework, we have had to duplicate 'test' into something else. Would the community think that such a formalization makes sense? tx, Vijay -- 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 rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout. -- 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 rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout. -- 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 rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
