

8·
3 days agoThe main question is - benefit to whom? Free software is like, take what you need, give what you can. Participating in projects where you can actually improve them and pass the improvements to others, who in turn improve something and pass them further, is the intended way of using it. Switch to what interests you, patch it, share patches, receive feedback, learn something, repeat. If you genuinely like NetBSD and believe you can make it better, go ahead, otherwise it’ll likely be a waste of time for everyone involved.

I have podman-compose on host. A single compose.yaml declares all images that should run and depend on each other. Then there’s a single .env file for config. A systemd user service runs
podman-compose upwith that .env file. A cron job periodically runs podman-compose pull, stops the systemd service, backups volumes and starts the systemd service back again. For the web app I write, its CI builds a Docker image and pushes it to the Codeberg registry, from which podman-compose picks it up. It’s very far from instant deploy, but works for my needs.