Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Heroku Button

blog.heroku.com

Post reply on HN
Print view View original

11–20 of 47 posts

Re: Introducing Heroku Button

#11

Post by andy_ppp »

timdorr wrote: post #9
benologist wrote: post #3

This is brilliant. Are affiliate links on the roadmap? That could create a great revenue stream for self-hosted projects.

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.

I imagine you need to set up your app to use Heroku. It's not very hard but beware that you can't write to the filesystem with Heroku so that would need to be factored in to the functionality of quite a few apps.

Re: Introducing Heroku Button

#12

Post by mschoening »

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

Re: Introducing Heroku Button

#14

Post by bjeanes »

andy_ppp wrote: post #11
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.

I imagine you need to set up your app to use Heroku. It's not very hard but beware that you can't write to the filesystem with Heroku so that would need to be factored in to the functionality of quite a few apps.

You can write to the file system, it's just not persistent across dyno restarts or shared across running dynos. Writing out for in-request work is fine.

Re: Introducing Heroku Button

#15

Post by sadkingbilly »

andy_ppp wrote: post #11
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.

I imagine you need to set up your app to use Heroku. It's not very hard but beware that you can't write to the filesystem with Heroku so that would need to be factored in to the functionality of quite a few apps.

Or replace writing to the file system with storing as a json object on one of many online (eg. cloud) providers.

Re: Introducing Heroku Button

#18

Post by aikah »

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 refactoring.

You'd need at least to enter some env variables to make things work,and the app would need to detect the db state and run migrations,if not properly initalized,when using a RDBMS(since again,sqlite is out of question on Heroku).

Re: Introducing Heroku Button

#19

Post by friism »

timdorr wrote: post #9
benologist wrote: post #3

This is brilliant. Are affiliate links on the roadmap? That could create a great revenue stream for self-hosted projects.

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.

Re: Introducing Heroku Button

#20

Post by friism »

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

Post reply on HN