Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "staging" environment in application.example.yml #279

Closed
pmackay opened this issue Nov 30, 2014 · 2 comments
Closed

Add "staging" environment in application.example.yml #279

pmackay opened this issue Nov 30, 2014 · 2 comments

Comments

@pmackay
Copy link
Contributor

pmackay commented Nov 30, 2014

Would be good to have consistent configuration for all standard environments.

@monfresh
Copy link
Member

Thanks for the comment. You are free to manage your environments however you choose, but we try to keep things as simple as possible, and configured according to best practices.

I used to think that a staging app needed to have its own "staging" environment, but after reading Heroku's recommendations, I now believe it's best to have the staging app run in the production environment so that it mimics the production app as closely as possible. If you need certain environment variables to be different for the staging app, you can set them manually.

Heroku makes it easy to fork your production app to create a "staging" app. Read the following articles for more details:

https://devcenter.heroku.com/articles/multiple-environments
https://devcenter.heroku.com/articles/deploying-to-a-custom-rails-environment

@pmackay
Copy link
Contributor Author

pmackay commented Dec 1, 2014

OK will try that approach. Thanks!

@pmackay pmackay closed this as completed Dec 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants