Live data from Hacker News

Introducing Heroku Button

blog.heroku.com

31–40 of 47 posts

Re: Introducing Heroku Button

#31
post #8

This is extremely clever. One of the reasons WordPress took off was the easy, non-technical install process.

That's 90% related too PHP. Not really Wordpress. I mean the whole setup LAMP is probably about as easy as it gets in regards to deploying something.

Re: Introducing Heroku Button

#33
post #26

Earlier quoted context omitted.

the font does look thinner but I like it (doesn't look any more invisible from my eyes)

The fact that on a Mac the font is thinner makes me wonder if you can even see it on Windows?

Judging by my windows machine and using just my eyes, yes, it's a little thinner, and no, there's no problem reading it. The faded-grey-ness of the words "to Heroku" is a much bigger legibility problem than the minor change in font weight.

Re: Introducing Heroku Button

#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 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?

Re: Introducing Heroku Button

#36

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.

Here you go (we'll update docs momentarily): https://cdn.herokuapp.com/deploy/button.svg

You should just convert to .svg the white icon, the rest of the button will look better in CSS.

Re: Introducing Heroku Button

#38
post #36

Earlier quoted context omitted.

Here you go (we'll update docs momentarily): https://cdn.herokuapp.com/deploy/button.svg

You should just convert to .svg the white icon, the rest of the button will look better in CSS.

That may be the case, but there's many contexts where you'd use this button where you can't alter the page's CSS. Perhaps the prime example being GitHub READMEs.

Re: Introducing Heroku Button

#39
This is amazing - this is something similar to the experience I want to provide for our internal engineering team.

Most developers get stuck on packaging their app, deploying it, managing it. This is one of those cases where it "just" works.

It would be really cool to try to replicate this in our AWS setup.

Guess I know what my weekend project will be :D

Re: Introducing Heroku Button

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

Quick edit: Here is the announcement email to the local railer's group https://groups.google.com/forum/#!topic/Mad-Railers/-1MkbbkX... To be clear, I have no reason to believe that Heroku used anything I made. Just wanted to self promote a bit.

Post reply on HN