Docker-compose was a limiting factor for me as well. I am seeing more and more projects that I deploy --- maybe 25 of the 50 I deploy a month -- using docker-compose.
I would love a simple docker-compose plugin, or a way to deploy with compose (I'd be okay if it gave a warning that 'may cause potential issues etc etc').
Do you have any resources on how to write plugins for dokku?
Again, I am extremely impressed by dokku and a big fan. I think a significant amount of your users would benefit from some way to use docker-compose. Would love to contribute.
Can't wait to see future releases!
Our plugin creation docs are here: https://dokku.com/docs/development/plugin-creation/
Most of the frustration just comes from a lot of existing projects I'd like to simply deploy rely on docker-compose, so instead of just cloning and deploying, I need to adapt things. So really it's not exactly a frustration with Dokku :P
There are a few technical and philosophical reasons we don't support compose out of the box:
Note that you can deploy compose to ACI and ECS, both of which have a bunch of caveats around usage[1][2]. The only Kubernetes support I'm aware of for compose is Kompose[3], which transforms the file to something kubernetes is aware of for application.I think overall the limitation around zero-downtime deploys in compose makes support in Dokku less interesting. We have support for basically everything you'd want otherwise. Our current alternative is to use dokkupose[4] to transform a compose file to the corresponding Dokku commands.
If folks are comfortable with the downtime and any other limitations, it might be nice to have a simple docker-compose plugin for building/scheduling, but I feel as though it wouldn't be worth it (maybe its just me).