It would also work out of the box for open-source apps that use docker-compose so you can deploy tools like Ghost, Umami, or Plausible with minimal setup.
Would this be useful to you? What features would you want for your use case?
It would also work out of the box for open-source apps that use docker-compose so you can deploy tools like Ghost, Umami, or Plausible with minimal setup.
Would this be useful to you? What features would you want for your use case?
Like the other response, my concern would be reliability on a new service, but I’d use it after it was around for a year or two.
Inevitably, if I had all the apps I want to spin at hands, I would need a very neat way to make sure path to upgrades are smooth, don't break things already in place and potentially used in "production" by either friends of family..
They suggest a platform where "you upload any docker-compose.yml". Consequently, this makes SSO, updates, etc. the user's responsibility.
I've not seen or used a docker-compose that was designed for production settings, it's primarily a dev time tool. Would we not have to maintain a second dc file with different settings?
Why not use Kubernetes for local dev (kind or minikube) instead of trying to make docker compose hacks for production? Docker Swarm is rarely seen, I suspect industry has already settled on k8s as the standard
I also wrote a simple script of how to deploy my apps and it works great. But I would, for sure, like to hear more about your idea. You plan to build someting like that?
mmarian•8mo ago
jsbroks•8mo ago