Autodiscover New Services in Repository Without Needing to Update doco-cd.yaml #728
Replies: 7 comments 9 replies
-
|
Good idea, I didn't think about something like this yet. Doing it this way will however require the users to always set the project name in the compose file: https://docs.docker.com/compose/how-tos/project-name/ |
Beta Was this translation helpful? Give feedback.
-
|
I'm working on the feature: #766 |
Beta Was this translation helpful? Give feedback.
-
|
I created a pre-release you can test. Please send me some feedback if this what you had in mind. |
Beta Was this translation helpful? Give feedback.
-
|
@epoch-philosophy Currently doco-cd always auto-deletes missing apps from the Docker host. I could add some sync-options (similiar to what argo-cd has), so you can for example disable the auto-delete. Edit: |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
The new release v0.50.0 is now available and contains this feature. :) |
Beta Was this translation helpful? Give feedback.
-
|
Looks like we got the feature! Thanks a ton! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! There's one feature/roadblock that is keeping me from migrating over to doco-cd! That's the ability to add new services/compose files in your directory without having to manually add them to doco-cd.yaml. This one is a huge bummer to me.
For example, in FluxCD in Kubernetes, you simply add new files to your repository (in this case of doco-cd, it would be a new docker-compose file!) and FluxCD will simply deploy them. To my knowledge this will not work in doco-cd. You have to manually add a new service to the doco-cd.yaml file which adds another layer of configuration to deploy containers. This is the one thing that bugs me about Portainer and Komodo. It's just another layer of configuration and work to do when deploying a stack.
If we can simply throw new docker-compose files into your repository, say: apps/service/compose.yaml and point doco-cd to scan the apps/ subdirectory without having to add new services in doco-cd.yaml, that would be an absolute game changer and would make this THE automation program for docker. Nothing would come close to it.
I think for now, because you need to manually add each new service file, there's not a huge reason for people to switch from Komodo to doco-cd unless you are resource starved! (I will add that the integration of SOPS and Swarm is a big plus!)
Anyhow, thank you for the work on this project. It has a ton of potential, but man, this feature would simply put docker git ops in near parallel functionality to Kubernetes. This would change everything.
(If doco-cd is capable of this and I'm an idiot please let me know. I couldn't get it to work this way.)
Beta Was this translation helpful? Give feedback.
All reactions