Thanks for the input. The environment variables was just what I was looking for.
Carl
2009/5/24 Harry Vangberg :
>
> Environment variables is probably the best choice here. Another
> solution I use on projects I put on Heroku before the config vars
> came, is to have a 'heroku' branch with that
Environment variables is probably the best choice here. Another
solution I use on projects I put on Heroku before the config vars
came, is to have a 'heroku' branch with that kind of specific stuff,
and then keep it in sync with master, and just pushing that one.
2009/5/23 Carl Anderson :
>
> Tru
True, I suppose it wouldn't matter, but it might be good to know how
to handle this for other keys that you don't want put onto something
like Github, but do want pushed out to remote production servers, like
Merchant account keys, etc.
Carl
On Sat, May 23, 2009 at 9:57 AM, Jeremy Lightsmith
wr
...do you really care if someone gets hold of your hoptoad api key? you
could use config vars, but why, what's the worst they can do with it...spam
your hoptoad account with spurious errors?
Jeremy
On Sat, May 23, 2009 at 9:55 AM, Ron Evans wrote:
>
> I think the proper way to handle this on h
I think the proper way to handle this on heroku is to use config
vars... this link show some examples for S3 that are very similar to
your needs:
http://docs.heroku.com/config-vars
On Sat, May 23, 2009 at 9:17 AM, Carl wrote:
>
> I would like to use Hoptoad for my project, but am I correct is
>
I would like to use Hoptoad for my project, but am I correct is
assuming I shouldn't get the hoptoad.rb config file into my Github
repo since it contains my api key? If so, how do I get it uploaded to
Heroku? I currently have two remotes configured, one for Github, and
one for Heroku.
--~--~--