Live data from Hacker News

A simple DIY Heroku replacement to keep your hosting costs down

github.com

1–10 of 76 posts

Re: A simple DIY Heroku replacement to keep your hosting costs down

#4

The usual counterargument is that DIY keeps your costs down if your time is free. Disclosure: I work for Pivotal, we have some overlap with what Heroku does.

The great thing about CaptainDuckDuck is that it expressly aims to address your argument. I haven't used it myself, but from reading his blog post (linked below), his goal is to build something 75% cheaper, but just as easy-to-use.

> My goal was to enable a typical web app developer create a Heroku-like server instance in less than 10 minutes. I am happy to say, I did it!

Re: A simple DIY Heroku replacement to keep your hosting costs down

#8
post #5

Well, Dokku [1] is already a good solution to the heroku cost problem. All the power and convenience of heroku commands with the freedom and low cost of docker deployment. It has lets-encrypt ssl support too! [1] https://github.com/dokku/dokku

I'm using Dokku to serve a bunch of sites and love it, it has made deployments a breeze. I did run into some Docker problems (used too much CPU and couldn't connect to its socket, etc), but I don't think it was Dokku's fault, but Docker's.

I want to see if I can use Kubernetes as a Dokku replacement (hopefully a more stable one), but I don't think Kubernetes has all the niceties Dokku has (automatic reverse proxying, Let's Encrypt support, etc).

Re: A simple DIY Heroku replacement to keep your hosting costs down

#9
post #8
post #5

Well, Dokku [1] is already a good solution to the heroku cost problem. All the power and convenience of heroku commands with the freedom and low cost of docker deployment. It has lets-encrypt ssl support too! [1] https://github.com/dokku/dokku

I'm using Dokku to serve a bunch of sites and love it, it has made deployments a breeze. I did run into some Docker problems (used too much CPU and couldn't connect to its socket, etc), but I don't think it was Dokku's fault, but Docker's. I want to see if I can use Kubernetes as a Dokku replacement (hopefully a more stable one), but I don't think Kubernetes has all the niceties Dokku has (automatic reverse proxying,…

Kubernetes can have automatic reverse proxying and let's encrypt via an Ingress controller. I don't doubt Dokku has some nice plugins that Kubernetes doesn't though, especially for developers.

Re: A simple DIY Heroku replacement to keep your hosting costs down

#10
post #4

The usual counterargument is that DIY keeps your costs down if your time is free. Disclosure: I work for Pivotal, we have some overlap with what Heroku does.

The great thing about CaptainDuckDuck is that it expressly aims to address your argument. I haven't used it myself, but from reading his blog post (linked below), his goal is to build something 75% cheaper, but just as easy-to-use. > My goal was to enable a typical web app developer create a Heroku-like server instance in less than 10 minutes. I am happy to say, I did it!

I think I worked out what my actual problem is here: pride.

I work on a platform partly inspired by Heroku and which consequently deals with many of the same problems. I am intimately aware of how much work has been required to build that platform and expand its capabilities.

It is hard to read someone saying they have replaced Heroku and not feel annoyance, because it downplays the enormous amount of careful engineering that Heroku and its competitors represent.

Post reply on HN