Is it certain that "CONFIG.merge! CONFIG.fetch(Rails.env, {})" will pull in heroku environment variables pulled in via heroku config:push from the .env file?
Minor not that may help folks if you aren't familiar with yml files (I am not) :
if you want to put your AWS account, access key, and secret access key in enviornment variables, you must use the <%= %> brackets to access them. For example :
access_key: <%= ENV["AWS_ACCESS_KEY"] %>
This is unlike other rails configuration files. I'm not quite sure why since yml files look ruby-ish.
watch on iTunes
follow on Twitter
follow on Facebook
subscribe to RSS feed
Is it certain that "CONFIG.merge! CONFIG.fetch(Rails.env, {})" will pull in heroku environment variables pulled in via heroku config:push from the .env file?
Minor not that may help folks if you aren't familiar with yml files (I am not) :
if you want to put your AWS account, access key, and secret access key in enviornment variables, you must use the <%= %> brackets to access them. For example :
access_key: <%= ENV["AWS_ACCESS_KEY"] %>
This is unlike other rails configuration files. I'm not quite sure why since yml files look ruby-ish.