Serious, non-sarcastic question: So now you have your own mini Heroku on your own VM somewhere. Is the probability of downtime now smaller than it was on heroku? It seems to be it would be higher...
Yes, but now you can at least plan/schedule downtime according to your particular needs, and unscheduled downtime is at least a little more transparent to you. Sounds like that's what the original article wanted, in any case.
That's a legitimate benefit, although I was suggesting it's offset by the greater chance of something going wrong when you are managing your own servers, especially if you're not an expert sysadmin. I would assume Heroku instances are secured better than a box you're locking down yourself.
Re:Goodbye Heroku
by mattgreenrocks on Monday June 23, 2014 @04:34PM
(#7934463)
Dokku is cool, but it is very basic. Deployed apps don't have any sort of restart protection, for instance.
Re:Goodbye Heroku
by king_magic on Monday June 23, 2014 @05:04PM
(#7934654)
It looks like it's possible with a Dokku plugin (https://github.com/statianzo/dokku-supervisord). But agreed, definitely basic - but I think it has a ton of potential.
The Dokku team is behind Flynn (https://flynn.io/) which has more features a la deis.
It took a few hours, but I was able to get my Heroku-based Rails app up and running on a Dokku droplet (to be fair, the most time-consuming part was getting the SSH keys right and figuring out that I needed a domain name - e.g., couldn't just set it up with a droplet's IP address - at least not with the DigitalOcean tutorial's instructions: https://www.digitalocean.com/community/tutorials/how-to-use-...).