dokku

Ok so I am researching what to use in this space - a Vercel-ish clone on cheap VPS - and, is Dokploy really the best option? What do you think about Caprover? https://github.com/caprover/caprover Or uh.. Dokku https://github.com/dokku/dokku Right now I am using Coolify but so far it has not been exactly reliable

I think there's a couple decent alternatives out there: https://alternativeto.net/software/heroku/ There are also a lot of cool "self-hosted Heroku" alternatives - Coolify (PHP) (2020) https://github.com/coollabsio/coolify - Dokku (Go) (2013) https://github.com/dokku/dokku - Dokploy (TypeScript) (2024) https://github.com/Dokploy/dokploy - CapRover (TypeScript) (2017) https://github.com/caprover/caprover - Komodo (Rust) (2022) https://github.com/moghtech/komodo

I was also looking at alternatives - K8S-based - https://github.com/cozystack/cozystack https://github.com/kubero-dev/kubero https://github.com/pluralsh/plural DCR-based - https://github.com/coollabsio/coolify https://github.com/dokku/dokku/ https://github.com/Dokploy/dokploy https://github.com/swiftwave-org/swiftwave Most of these projects are maintained by a single maintainer; for business critical apps look elsewhere.

Looks like dokku is also a MIT Licensed open source project[1]. Note that there is also Dokku Pro[2], one time purchase during beta, offering UI and API. [1]: https://github.com/dokku/dokku/ [2]: https://pro.dokku.com/

I don't think that's true. I opened https://github.com/dokku/dokku/issues/5008 a while back and Jose didn't seem to disagree. Addressing your argument directly though: you know that if you spin up a Postgres database for your app, you need to dump the database to disk to back it up (or if you wanna get fancy, you can do a delta from the last backup + a full backup periodically). Anytime a Postgres database exists, you know the steps you need to take to backup that service. Same with persistent file storage on disk: if you have a directory of files, you need a snapshot of all of those files. Each _service_ can know how to back itself up. If you tell a Dokku _app_ to back itself up, what you really mean is that each _service_ attached to that app should do whatever it needs to do to create a backup. Then, dokku only needs to collate all of

I love the minimal approach - will try it! There is also: https://kamal-deploy.org/ https://github.com/basecamp/kamal https://dokku.com/ https://github.com/dokku/dokku/ https://clace.io/ https://github.com/claceio/clace

Yeah there are a bunch of selfhostable things: Caprover (https://caprover.com/) Dokku (https://github.com/dokku/dokku) But people still choose Netlify and Vercel for ease of use I think. Maybe we need something that's just Netlify. The closest I've seen to the "right" UX is Ness: https://ness.sh Though of course it's a tui so some people will get turned off of that (especially people who are willing to spend).

Dokku [1] is a self-hosted alternative that can be hosted on any IaaS 1: https://github.com/dokku/dokku/

dokku on a vps? ref: https://github.com/dokku/dokku

Dokku is another option if you are looking for something open source that you can run on a VM on any cloud. https://github.com/dokku/dokku

I thought about this a bit last night and did some research. I think with the evolved compose file format, this is more doable (though still with routing downtime until I do some extra work). I've filed a ticket for this here: https://github.com/dokku/dokku/issues/5102 Our plugin creation docs are here: https://dokku.com/docs/development/plugin-creation/

I thought about this a bit last night and did some research. I think with the evolved compose file format, this is more doable (though still with routing downtime until I do some extra work). I've filed a ticket for this here: https://github.com/dokku/dokku/issues/5102

Dokku maintainer here. Dokku is still chugging along, and has 3-4 big releases a year, with patch releases every so often. We also have partial support for Kubernetes and Nomad, and our Kubernetes integration in particular is in use in a variety of Fortune 500 companies. Some folks are interested in Swarm support[1] as well. I also recently released a "pro" version[2] for folks that want/need extra functionality that doesn't quite make sense for the typical "I have a single server and its just me using it" situation All that said, we're here to stay, and I don't think we're losing any steam :) - [1] https://github.com/dokku/dokku/issues/4486 - [2] https://pro.dokku.com/

One approach that has worked for me so far is: 1) find out if the runtime/framework is supported but Heroku or if there are any buildpacks available. 2) spin up a Dokku instance using Vagrant for local development and testing 3) deploy to a live Dokku server If/when I encounter any issues I add Heroku or Dokku to my search query and 9 times out of 10 I’ll find an answer to my issue. Else I just dig into the Dokku docs and GitHub issues and figure it out. So for instance googling for deploying a Phoenix app with Dokku results in a few hits such as this one [0]. There's also a lovely UI for Dokku being actively developed: Ledokku [1] The only drawback currently is when you want to horizontally scale your deployment. You can use their kubernetes or nomad schedulers but I think those are an overkill in terms of complexity. You could also use

I really wish Dokku would embrace docker swarm like caprover. Currently they have a scheduler for kubernetes but the docker swarm scheduler is indefinitely delayed [0]. It’s like the missing piece to making Dokku a real power tool for small teams. Currently, if you want to scale Dokku horizontally and aren’t ready to take the kubernetes plunge, you have to put a load balancer in front of your multiple VMs running Dokku and that comes with it’s own headaches. [0] https://github.com/dokku/dokku/projects/1#card-59170273