I've spent a while recently migrating my personal infrastructure off Coolify . Coolify 's an excellent tool and one that helped manage the initial learning curve of managing and deploying things when I started to self host things. As I got more comfortable with the process, issues and details I found myself wanting to remove it as an abstraction on top of what I had become comfortable managing.
All of my projects are now stored on my Forgejo instance rather than GitHub as the latter continues to speed run the enshittification curve. I've implemented a manual deploy button in my site's admin but for other, lighter-weight projects, I prefer to deploy changes whenever I push them up.
I have Coolify building my site and rsync -ing the build output to a separate LAMP server. There was a recent bug in a release that broke compatibility with Nixpacks that broke my previous deployment configuration. To the Coolify team's credit they pushed out a fix within hours (and noted that Nixpacks often has issues where it may break).
"What did you do over the break?" "I moved everything to my own hosting!" ... I mean, that's hardly everything and it's far from the most important thing (or set of things) that I did, but it is a thing .