Heroku scheduler and environment variables about cutiesinhamptonroads

[qwo]

@boonrs @drewrwilson maybe you could chime in on this

maybe boston cc. @ohnorobo @beechnut

edit: beaten to the punch! good work Linda
edit2: I'm pretty sure we should be doing work. but this is too much fun!

[lynnaloo]

This is the original issue codeforboston#17

[ohnorobo]

One note:

The Denver repo uses a template.env file instead of the .env file we're using in the Boston repo.
Maybe that interacts differently with heroku?

[beechnut]

Their template.env is just a template for a .env. I think their README says to copy it to .env and fill in vars.

[lynnaloo]

Both template.env and .env are .gitignored so it's just like you are in Boston. We use a sample.env in a similar fashion. For Heroku, you add config values for each one of the environment variable and normally the application uses them correctly and it seems almost too easy. In this case, the heroku forum suggests that when the rakefile is built, it doesn't have access yet to those configs.

[lynnaloo]

This was happening because I had single quotes around the shelter_id environment value. @metaskills helped me debug.