I only clicked this to see if Coolify could be a compelling option against my current setup, of using Docker Compose for everything on my VM (including a private Docker registry for my images, and a Traefik frontend proxy to route it all).
Zero actual mention of Coolify, and the manual steps to PREPARE for it seem far more complicated than, "Just base your VM on the Docker Compose base image, and then tweak a couple things".
I'll stick with what I have. Nice advantage is that I can migrate from host to host and 99% of it is just copying the Docker Compose YAML file.
Until coolify and similar projects support DB backups with streaming replication, it will just remain as a hobby project and won’t be used for anything customer facing.
Docker compose and bash script is all I need to run 2 vms, with hourly backups to s3 + wal streaming to s3 + PG and redis streaming replication to another vm. That is bare minimum for production
Any pointers in how you run the backups and Wal streaming?
Not the original commenter, but I've used https://github.com/wal-g/wal-g before for this and had a good experience with it.
If you haven't done so already, I'd highly recommend reading the postgres documentation about continuous backups before setting it up, as it teaches the fundamentals: https://www.postgresql.org/docs/current/continuous-archiving...
I tried it a few months back but as soon as you want a project that has multiple containers using compose all sorts of issues start popping up. Like it "forgets" which containers it started and then can't stop them any more or now you have 2 containers of the same service running even though coolify only recognizes one.
I think if you do register each service separately in coolify it runs OKish.
But I've now switched to the same setup as you had and ironically it has been so much simpler to run than coolify.
I'm really happy people are working on projects like coolify, but currently it's far from ready for any serious use (imo).
Coolify still requires root for installation, though they have a branch that doesn't that they're working on.
So you can just ssh in and do the coolify install and then switch off root login I guess, if you're willing to just blow away the server and start over if you ever needed to ssh in again.
I tried a from scratch coolify deploy recently and it kept failing with ssh key errors. On the other server we have it working and deploying many projects however the "just give it a docker compose" method has never worked for us.
Coolify uses Traefik and Docker under the hood and is really just a UI for it. It's definitely missing some critical backup features (solvable through restic or similar) and the UX is... good enough but no better.
it depends on your usecase, but i tried both coolify and caprover.
ended up going with caprover because i can more quickly spin up a nodejs app on there with git hooks (so it builds on each commit to a specific branch).
both offer this functionality, there's just less friction on caprover. but coolify is probably more extensive.