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

[Support] Briefest of brief production environment setup docs #903

Closed
patcon opened this issue Dec 28, 2016 · 3 comments
Closed

[Support] Briefest of brief production environment setup docs #903

patcon opened this issue Dec 28, 2016 · 3 comments

Comments

@patcon
Copy link
Contributor

patcon commented Dec 28, 2016

I know that you guys are definitely not interested in supporting others running your code, but I was wondering whether you might have any quick pointers on what envvars and services must run on prod environment. (In particular, I'm trying to get it running on heroku, but that's not so much important.)

Right now, these were my assumptions:

  • Created heroku env with
  • Created a Procfile.production without the mail process.
  • Create a .env.production with:
    • RAILS_ENV=production
    • smtp_settings for sendgrid
  • Run via heroku local -f Procfile.production -e .env.production

This is what I get (the url show that i was running rack, but same experience when running default webrick rails server):

screenshot of 500 error

@monfresh
Copy link
Contributor

Hello. All the necessary configuration is in application.example.yml, which gets copied to your local machine as application.yml. We use the Figaro gem for configuration, and it comes with a handy command that will set all the proper env vars on Heroku based on the values in application.yml:

$ figaro heroku:set -e production

@monfresh
Copy link
Contributor

Also, if you look at your Heroku logs, you should see a helpful message about what went wrong, most likely a message from Figaro saying that a required key was not set.

@patcon
Copy link
Contributor Author

patcon commented Dec 28, 2016

Thanks @monfresh. If you folks are giving me the above advice (ie. you expect it should Just Work), I'm going to assume I am making a silly mistake that I should be embarrassed about...! :)

I'll do some sanity checks and am happy to submit any doc clarification that might help the next person. Really appreciate the nudge in the right direction. Sorry for the noise!

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

3 participants