Comments on: Config vars and Heroku

By: B Seven

B Seven — Sun, 21 Aug 2011 02:01:58 +0000

Whenever you change the config, you have to rerake the task. Then do you verify that the change was made successfully? Also, is it a good idea to store sensitive info on your local machine?

Don't have a better solution yet, but I am still looking…

By the way, I don't see a date on this post. It's useful because Rails is changing so fast…

By: Heroku Tips for the Cheap | IONCANNON

Heroku Tips for the Cheap | IONCANNON — Tue, 12 Jan 2010 12:21:13 +0000

[...] For configuration Heroku has a way but for some reason it didn't seem like the best or easiest way to do things. I started off setting up a configuration file as described in this railscast on using yaml configuration files. I took a while to dig a little more and found something similar but even better way of doing configuration with Heroku. [...]

By: Heroku: A True Love Story « tinyHippos

Heroku: A True Love Story « tinyHippos — Thu, 07 Jan 2010 18:33:39 +0000

[...] Config var and Heroku [...]

By: Mark McEahern

Mark McEahern — Wed, 18 Nov 2009 08:17:14 +0000

I naively "improved" this by issuing the `heroku config:add` separately for each variable. This fails silently: Only the last one appears to stick. I think it's related to the fact that `heroku config:add` triggers an app restart. Anyway, it's probably worth noting something about this in your script–why the way you did it, building up the command, and issuing it in one fell swoop, is important.

Thanks!

Mark

By: Brian Hogan

Brian Hogan — Fri, 26 Jun 2009 10:46:51 +0000

That's pretty much what I did for mentors. config.yml and database.yml are ignored, config.example is included for devs to use, but in production we simple use ENV instead of the yml.

By: Trevor

Trevor — Thu, 25 Jun 2009 23:05:23 +0000

Yeah, I totally agree, but I think I did include that in the example .gitignore above…?

By: Pat Nakajima

Pat Nakajima — Thu, 25 Jun 2009 22:17:34 +0000

The one thing I'd add, for open source projects at least, is to .gitignore that config/config.yml file. That'll make it as easy as possible to clone, setup, and deploy an app to Heroku, while keeping things easy to set up. I've meaning to do so with my Aintablog project (http://github.com/nakajima/aintablog) for a while now. Your post just reminded me.