Remote docker compose update via Git

[NewStorm]

I have a bit of a different setup where I have a monitoring VM which runs Grafana, Prometheus and WUD and a second VM which is my general purpose docker host.
Most of my compose stacks are deployed via Portainer while some unique ones are directly deployed via docker compose.
Autoupdating this is quite messy.

To get this done I've had a flash of my mind:

• Moving all docker-compose files into a git repo which feeds Portainer and the direct deployments
• Let WUD update the version tags of the yaml files
• Push them to the git repo
• portainer redeployes via hooks

Advantages:

• Great rollback options
• Neatly organised compose files
• Very flexible

Disadvantage:
Thats not (yet) implemented 😄

While I am not a javascript pro, I would be interested in trying to implement this (maybe by reusing some existing compose update code)
Would this be a useful feature and worth the effort ?

[IARI]

I would absolutely want to use this feature - kind of.

I don't really need the git/roillback control, I have tried to use git-versioned compose files from portainer in ther past and had some hickups (but I forgot what it was exactly) which made me not really like the feature.
I would personally prefer to not have to migrate all docker-compose to a git repo, even though portainer supports it.

I understand your needs are different, but I suppose it could also be implemented without the git-versioning - i.e. just by directly reading/writing the docker-compose part of portainer-stacks.
Maybe even somehow using environment variables which could be useg in the docker-compose for the version tags of the respoective images.