miko VS pcompose

If you can afford a DigitalOcean/Linode/Hetzner , Polybox https://github.com/mardix/polybox may allow you to host multiple applications on a single servers. With SSL and Git-push similar to Heroku.

For a simpler option without Docker, but still with GIT Heroku-style, check out Polybox[0].

Polybox[0] is an itty-bitty PaaS that uses git push to deploy micro-services and websites on your own servers.

[0]https://github.com/mardix/polybox

I made a small app to do this: https://github.com/antoniomika/pcompose

I made a tool that does exactly this [0] wrapped up in a tiny little server! Main reason I did that was because I found myself creating "compose apps", where it was some self-hosted thing that I spent a lot of time managing without version control or in a deterministic manner.

For ingress, nginx-proxy (or traefik or caddy) listens for when a container starts on the network (auto attached by pcompose) but you still have all of the flexibility of docker-compose. Build happens on push if you have that defined in compose, so on and so forth.

Was able to even create some simple "convenience" ssh methods where you can trigger docker-compose commands or tail logs/exec into container directly over ssh. Definitely super crude and not really for production, but works great for apps that I just want to run and forget about.

[0] https://github.com/antoniomika/pcompose