Use experimental user-env-compile heroku addon

It seems that heroku generally denies us access to ENV['...'] during asset
compilation. They have reasonably good reasons for this, and yet I don't
know how else we're meant to get at our API keys (other than hardcoding
them into our config files, which we don't want to do).

So, to work around this, I'm recommending the use of the (experimental,
subject to removal/change, sigh) user-env-compile heroku addon.  This
lets us use ENV during asset compilation.

For more info see
https://devcenter.heroku.com/articles/labs-user-env-compile
This commit is contained in:
Skud
2013-09-11 17:30:21 +10:00
parent b39df447b6
commit 8a203deb19

View File

@@ -15,3 +15,11 @@ rake growstuff:oneoff:set_planting_owner
echo "2013-08-26 - initialize member planting count"
rake growstuff:oneoff:initialize_member_planting_count
echo "2013-09-11 - Maps setup"
echo "************************************************************************"
echo "Did you remember to:"
echo "heroku labs:enable user-env-compile -a myapp"
echo "heroku config:set CLOUDMADE_KEY=..."
echo "(if not, rollback, do it, and then re-deploy.)"
echo "************************************************************************"