Introducing Heroku Button • Hacker News Board

Re: Introducing Heroku Button

#21

Post by ryanbrainard » Thu, Aug 07, 2014, 6:28 PM UTC

timdorr wrote: post #10

Does this have to work only via Github? Any chance it can support any arbitrary Git URI?

The button only works with GitHub repos at this time, but if you can place the button on other sites by using the ?template= parameter to point back to the GitHub repo. If you would like to have an app.json in a non-GitHub repo (or any source in a tarball for that matter), you can use the app-setup API (https://devcenter.heroku.com/articles/platform-api-reference...) to do the deployment.

Re: Introducing Heroku Button

#22

Post by benologist » Thu, Aug 07, 2014, 6:28 PM UTC

friism wrote: post #19

timdorr wrote: post #9

Earlier quoted context omitted.

Does this support normal Git links? If so, you could simply link to a Gumroad or similar site and have that send a Heroku Button link with a customized git repo where they can deploy from.

Right now buttons only work with source code hosted on GitHub (although the button can be added anywhere). We want to extend that to other source code hosting services, though.

How about linking to a zip or tar file?

Re: Introducing Heroku Button

#23

Post by pooper » Thu, Aug 07, 2014, 7:10 PM UTC

mschoening wrote: post #12

MaxGabriel wrote: post #4

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

Very impressive

Re: Introducing Heroku Button

#24

Post by Dorian-Marie » Thu, Aug 07, 2014, 7:20 PM UTC

Awesome, can't wait for "Deploy Discourse to Heroku", "Deploy Jekyll to Heroku", ...

Re: Introducing Heroku Button

#25

Post by danielweber » Thu, Aug 07, 2014, 7:33 PM UTC

mschoening wrote: post #12

MaxGabriel wrote: post #4

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

I'm not on a retina display but that doesn't look as nice. The letters are so thin they start to disappear even before using the light-purple-on-dark-purple font.

Re: Introducing Heroku Button

#26

Post by yutah » Thu, Aug 07, 2014, 7:42 PM UTC

danielweber wrote: post #25

mschoening wrote: post #12

Earlier quoted context omitted.

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

I'm not on a retina display but that doesn't look as nice. The letters are so thin they start to disappear even before using the light-purple-on-dark-purple font.

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

Re: Introducing Heroku Button

#27

Post by derwiki » Thu, Aug 07, 2014, 7:55 PM UTC

Dorian-Marie wrote: post #24

Awesome, can't wait for "Deploy Discourse to Heroku", "Deploy Jekyll to Heroku", ...

It would be a great "growth hack" for services like that

Re: Introducing Heroku Button

#28

Post by Artemis2 » Thu, Aug 07, 2014, 8:08 PM UTC

friism wrote: post #20

timdorr wrote: post #10

Does this have to work only via Github? Any chance it can support any arbitrary Git URI?

Right now buttons only work with source code hosted on GitHub (although the button can be added anywhere). We want to extend that to other source code hosting services, though. The challenge is that we have to resolve the [app.json][1] file to generate the deploy UI. [1]: https://blog.heroku.com/archives/2014/5/22/introducing_the_a...

Why not do something like the go get tool, that uses git, mercurial and subversion to try to resolve a repo by a URL and to get its contents?

Re: Introducing Heroku Button

#29

Post by toadkicker » Thu, Aug 07, 2014, 8:28 PM UTC

aikah wrote: post #18

ceejayoz wrote: post #8

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

> This is extremely clever. One of the reasons WordPress took off was the easy, non-technical install process. Ironically Wordpress is a pain in the ass to deploy on "non persistent/deploy with git" PAAS.And uploading plugins directly through the admin is a no go in these cases. Worpdress wouldnt deploy directly with that one click install,given the fact the configuration is hardwritten on the disk.It would need some…

All the same that Wordpress could easily adopt using environmental variables for configuration values to achieve this and simply use a heroku-ified version of config.php. I've used this approach for scaling wordpress sites and its never failed me.

Re: Introducing Heroku Button

#30

Post by dubcanada » Thu, Aug 07, 2014, 8:52 PM UTC

yutah wrote: post #26

danielweber wrote: post #25

Earlier quoted context omitted.

I'm not on a retina display but that doesn't look as nice. The letters are so thin they start to disappear even before using the light-purple-on-dark-purple font.

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?