Awesome - I mentioned this 400+ days ago when the platform API was announced! Cool to see it getting rolled out, looking forward to playing around with this.<p><a href="https://news.ycombinator.com/item?id=5793441" rel="nofollow">https://news.ycombinator.com/item?id=5793441</a><p>EDIT: Setup was pretty smooth - one click deploy for my RSS reader now: <a href="https://github.com/swanson/stringer" rel="nofollow">https://github.com/swanson/stringer</a>
Heroku should consider using SVG for the badge, just like shields.io and services like Travis CI do. The current button is blurry on a retina screen, and basic SVG is really well supported.
I actually built this exact thing myself last year: <a href="https://github.com/southpolesteve/deploy_button" rel="nofollow">https://github.com/southpolesteve/deploy_button</a><p>Here is a repo that has the button included: <a href="https://github.com/southpolesteve/lucre" rel="nofollow">https://github.com/southpolesteve/lucre</a><p>Obviously I never really promoted it and I'm glad to see that Heroku built something official. But maybe someone far in the future will see this comment and remember :)<p>Quick edit: Here is the announcement email to the local railer's group <a href="https://groups.google.com/forum/#!topic/Mad-Railers/-1MkbbkXrYg" rel="nofollow">https://groups.google.com/forum/#!topic/Mad-Railers/-1MkbbkX...</a> To be clear, I have no reason to believe that Heroku used anything I made. Just wanted to self promote a bit.
There's a small gallery of Heroku button templates at <a href="https://clone.herokuapp.com/" rel="nofollow">https://clone.herokuapp.com/</a>
I think they're still working out the kinks [1], but nevertheless, great when it works. No more 'behind' hosted demos for open-source apps, just let them instantly deploy it and play with it on their own.<p>[1] Tried the sample node.js app immediately, although I am getting "Deployed to heroku", viewing it throws a "No such app" - <a href="https://www.dropbox.com/s/bsl55sia46ymrwv/Screenshot%202014-08-07%2019.24.13.png" rel="nofollow">https://www.dropbox.com/s/bsl55sia46ymrwv/Screenshot%202014-...</a>
This is amazing - this is something similar to the experience I want to provide for our internal engineering team.<p>Most developers get stuck on packaging their app, deploying it, managing it. This is one of those cases where it "just" works.<p>It would be really cool to try to replicate this in our AWS setup.<p>Guess I know what my weekend project will be :D
> Note that the snippet is repo-agnostic: It can be copy-pasted without modification and will work correctly if forked to a different repo. Heroku resolves the repo originating a button click by inspecting the referer header.<p>Is the referer reliable enough on modern browsers to assume this? Perhaps coming from an analytics perspective, we see all types of query-string hacks so that you can attribute the sources of links everywhere... so it's surprising to see a company depend on this functionality in a product. I suppose almost all developers would be using a browser that correctly sends referer headers... is this the case?
Nice - nitrous.io has had this for awhile in their Hack Button (<a href="https://www.nitrous.io/hack" rel="nofollow">https://www.nitrous.io/hack</a>), and I always thought it was pretty cool.
This is amazing, it's a simple app but <a href="https://github.com/aaronbassett/Bad-Tools" rel="nofollow">https://github.com/aaronbassett/Bad-Tools</a> only needed 1 single line change to work. Really impressed although I do need to read up more on the app.json schema.
Howsabout an app that performs terribly and does nothing - except teach you to improve your Ruby code?<p>Yeah, there is a button for that <a href="https://github.com/newrelic/newrelic-ruby-kata" rel="nofollow">https://github.com/newrelic/newrelic-ruby-kata</a>
Anyone else having a lot of problems getting it to work. I keep getting a "Something went wrong" message with no additional information. Even if I create a minimum viable app.json, nothing seems to work.
Kudos, now that's good business: it benefits both the company (because once you're there and it works, you're less likely to switch to another host) and the users who want to quickstart something.