-
Notifications
You must be signed in to change notification settings - Fork 308
deploy branches to heroku automatically #1133
Comments
Note that Heroku deploys master, so you have to do Or possibly |
It's |
Yeesh. I just hand-rolled another Gittip instance on Heroku. That was ... something that could be optimized. |
I wonder whether we can leverage Heroku buildpacks to do this. Circle back here after #1257. |
Dropping from Infrastructure. This is advanced infrastructure. |
@clone1018 found http://prune.io/ for this. IRC |
Assuming each branch gets deployed to a brand new Heroku instance, is there a limit to the number of free Heroku instances you can have? |
@seanlinsley I'm pretty sure it's fine so long as you're not using the extra instances to get around paying for extra dynos |
cc: @patcon |
+1 from @techtonik at #3718 (comment).
|
|
|
The page in the last comment seems to be pulled back. I guess the service is still beta. Will it be free for our purpose? |
Looks like they have a broken redirect on the blog post. Here's the correct link: https://blog.heroku.com/heroku-review-apps-ga. |
I've updated the link in my comment. |
As the issue isn't user-oriented, reticket to inside. |
We need this to turbo-charge our development workflow (@corytheboyd and @warreng called it; props). The idea is that any branch in GitHub gets its own public deployment, with its own database with fake data. This should be a subcommand of
gittip
.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: