Heroku button

[carols10cents]

NOTE: this includes the commits in #812 because i couldn't get it to work without them.

This adds a "Deploy to heroku" button to the README; I successfully deployed a new instance of rstatus from the button on my branch.

This creates a free rstatus instance in minutes with very little info needed from the end user (if they already have a heroku account, and assuming everything works).

I went with the most bare-bones configuration-- no twitter integration (we really should disable all twitter related buttons when those env vars aren't set), no elastic search. Those could be added without increasing the cost, but do add complexity. They certainly could be added later but hey, MVP!

[wilkie]

:O WHAT. THAT'S AMAZING OK HOLD ON GONNA REVIEW

[wilkie]

THIS IS JUST MAGIC

[carols10cents]

yes it is!!! :) :) :) it doesn't really help if people want to update the version they're running, but oh well, it's pretty amazing.

[wilkie]

hmm that is a problem that should be solved. maybe make an issue for it. I wonder what kind of strategy would be good for that.

[wilkie]

It must figure out where the app.json is from the referer (sic) Neat. LGTM!

[carols10cents]

yup :)

it looks like heroku's build api could potentially support an "update my heroku app to this version" button someday: https://devcenter.heroku.com/articles/build-and-release-using-the-api

[wilkie]

Seems generic enough that other hosting services might just reuse the app.json standard. Neat!!

[dominic]

Seems generic enough that other hosting services might just reuse the app.json standard. Neat!!

:smile: :smile: :wink:

[wilkie]

hehehe, well, heroku is a great trendsetter and we love them for everything.