Introducing Heroku Button • Hacker News Board

Re: Introducing Heroku Button

#41

Post by southpolesteve » Fri, Aug 08, 2014, 1:29 AM UTC

I actually built this exact thing myself last year: https://github.com/southpolesteve/deploy_button

Here is a repo that has the button included: https://github.com/southpolesteve/lucre

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 :)

Re: Introducing Heroku Button

#42

Post by michaelmior » Fri, Aug 08, 2014, 1:52 AM UTC

btown wrote: post #34

> 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. 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 li…

They do mention an alternative where you can set stuff in the query string. I'd probably rather do that instead. Especially since you could easily end up putting that button out of the context of your repo at some point and have it end up completely broken.

Re: Introducing Heroku Button

#43

Post by michaelmior » Fri, Aug 08, 2014, 1:53 AM UTC

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.

Re: Introducing Heroku Button

#44

Post by dinkumthinkum » Fri, Aug 08, 2014, 4:26 AM UTC

I think this is a pretty innovative marketing ploy. Seems to make a blog post very Heroku centric if you add this button but I see the benefits.

Re: Introducing Heroku Button

#45

Post by wildpeaks » Fri, Aug 08, 2014, 9:24 AM UTC

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.

Re: Introducing Heroku Button

#46

Post by coopr » Fri, Aug 08, 2014, 4:26 PM UTC

Howsabout an app that performs terribly and does nothing - except teach you to improve your Ruby code?

Yeah, there is a button for that https://github.com/newrelic/newrelic-ruby-kata

Re: Introducing Heroku Button

#47

Post by cben » Sat, Aug 09, 2014, 9:41 PM UTC

michaelmior wrote: post #42

btown wrote: post #34

> 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. 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 li…

They do mention an alternative where you can set stuff in the query string. I'd probably rather do that instead. Especially since you could easily end up putting that button out of the context of your repo at some point and have it end up completely broken.

But if I fork a repo with a button (or even navigate to different branch/commit in same repo), a manually set query string would still point to the same code. Whereas the referer headear can identify exactly the right version briliantly.