#!/bin/bash

# tasks to run at deploy time, usually after 'rake db:migrate'

# When adding tasks, do so in chronological order, and note the date
# when it was added.  This will help us know which ones have been run
# and can safely be commented out or removed.

# Default format is:
# echo "YYYY-MM-DD - do something or other"
# rake growstuff:oneoff:something

echo "2013-08-26 - set planting owner"
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 "************************************************************************"

#!/bin/bash

# tasks to run at deploy time, usually after 'rake db:migrate'

# When adding tasks, do so in chronological order, and note the date
# when it was added.  This will help us know which ones have been run
# and can safely be commented out or removed.

# Default format is:
# echo "YYYY-MM-DD - do something or other"
# rake growstuff:oneoff:something

echo "2013-08-26 - set planting owner"
rake growstuff:oneoff:set_planting_owner

echo "2013-08-26 - initialize member planting count"
rake growstuff:oneoff:initialize_member_planting_count

--- 
+++ 
@@ -15,11 +15,3 @@
 
 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 "************************************************************************"
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
