If you do $ heroku console 'ENV'
on your app, you'll notice that all heroku apps already have a COMMIT_HASH environment variable that's the last git push/commit revision. You can simply use this instead of defining your own config variable. K. --- http://blitz.io @pcapr On Fri, Aug 5, 2011 at 1:37 PM, dblock <dblockdot...@gmail.com> wrote: > We use a CDN for our content. Every new push to heroku changes the > value of ASSETS_HASH to the git-revision of the latest change. Then > the system reads that value to make URLs. > > I don't want to commit a file that contains ASSETS_HASH because that > becomes a chicken-egg problem (a hash that represents the ... previous > commit, umh...), I am super happy with our heroku config:add > ASSETS_HASH=... . But that restarts the server, after which I am > pushing the new code, maybe 30 seconds later. > > Is it possible to combine those two? I see two options. > > - git push heroku master +++config:add ASSETS_HASH=... > - heroku config:add ASSETS_HASH=... --norestart ; git push heroku > master > > Ideas? > > Thx > dB. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
