Dokku VS Docker

When I came across Coolify, I thought of giving it a try. I am aware of Dokku, but I never really tried it because it doesn't have a UI. I work primarily as a UI developer, so having a nice UI to work with is a plus for me.

I run all my projects on Dokku. It’s a sweet spot for me between a barebones VPS with Docker Compose and something a lot more complicated like k8s. Dokku comes with a bunch of solid plugins for databases that handle backups and such. Zero downtime deploys, TLS cert management, reverse proxies, all out of the box. It’s simple enough to understand in a weekend and has been quietly maintained for many years. The only downside is it’s meant mostly for single server deployments, but I’ve never needed another server so far.

https://dokku.com/

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

The modern iteration of these tools has taken the developer experience learnings from the Platform as a Service (PaaS) category, and will bring them to your own VM, giving you your own personal PaaS. Example of this include Dokku, Coolify, Caprover, Cloud66 and many more!

Based on the fact that your ideal is to have a similar experience to heroku than managing your own server setting up reverse proxies take a look at these options:

1) https://dokku.com - lets you turn your light sail instance basically into heroku

2) https://render.com

3) https://fly.io

4) If you have aws credits this is their heroku equivalent: https://aws.amazon.com/elasticbeanstalk

above is not what I do but would be the options I would pursue if I understand your preference and requirement correctly.

All in all, I really recommend trying out Dokku if you are a developer interested in hosting your own projects. It makes it super easy to get everything you need to get up and running without having to worry about the specifics. And the price is impossible to beat!

The installation instructions are on the frontpage of our site. Thats basically all you need to do to install Dokku. As far as using it, we have a simplified tutorial here.

Dokku is a lightweight and open-source PaaS platform that simplifies application deployment by leveraging Docker. With Dokku, developers can easily push their applications using Git, allowing Dokku to build and run them in isolated containers. Its CLI-only approach and plugin architecture make it highly extensible. Dokku's modular plugins enable features like database integration, Let's Encrypt SSL certificates, and automated Slack notifications, giving developers flexibility and control over their PaaS environment.

Also https://dokku.com/

I'm not touching anything Docker anymore.

Here's the scenario: you're the unfortunate soul who received the first M1 as a new employee, and nothing Docker-related works. Cue multi-arch builds; what a rotten mess. I spent more than a week figuring out the careful orchestration that any build involving `docker manifest` needs. If you aren't within the very fine line that buildx assumes, good luck pal. How long has `docker manifest` been "experimental?" It's abandonware.

Then I decided it would be smart to point out that we don't sign our images, and so I had to figure out how to combine the `docker manifest` mess with `docker trust`, another piece of abandonware. Eventually I figured out that the way to do it was with notary[1], another (poorly documented) piece of abandonware. The new shiny thing is notation[2], which does exactly the same thing, but is nowhere near complete.

At least Google clearly signals that they are killing something, Docker just lets projects go quiet.

How long before this project lands up like the rest of them? Coincidentally, we were talking about decoupling our CI from proprietary CI, seeing this was a rollercoaster of emotions.

[1]: https://github.com/notaryproject/notary