support multiple composes in one repo

[jotka]

support multiple composes in one repo

[v1rusnl]

Are we talking about a linked git?

I added my personal config git repo. When creating a new stack, I just link the Compose to the path in the Repo (e.g. /Server1/dockhand/docker-compose.yml) and it works. It also works, if it's a folder with multiple repos. Or am I misunderstanding something?

Nicer would just be a small directory structure browser for git repos imo.

[eximo84]

Thanks for this, so my structure for my single repo

REPO
|__ Applications
     |__ Gitea
          |__ docker-compose.yaml
          |__ .env
     |__ Donetick
          |__ docker-compose.yaml
          |__ .env
|__ Monitoring
     |__ Uptimekuma
          |__ docker-compose.yaml
          |__ .env

I have multiple compose files within a single repo, separated by individual folders

[BartschLabs]

Nicer would just be a small directory structure browser for git repos imo.

@v1rusnl, isn't browsing the git repo pretty fast and easy to do within your git system?

BTW, personally I can also quite quickly browse the repo clones that Dockhand creates because I have Dockhand's /app/data redirected to my NAS.

[v1rusnl]

@v1rusnl, isn't browsing the git repo pretty fast and easy to do within your git system?

Sure, I meant it would be nice to be able to be able to navigate through the repo folders when creating a stack for users that have a repo for multiple compose stacks..

BTW, personally I can also quite quickly browse the repo clones that Dockhand creates because I have Dockhand's /app/data redirected to my NAS.

Yeah my folder structure from the other server are not mounted to dockhand.

[BartschLabs]

Sure, I meant it would be nice to be able to be able to navigate through the repo folders when creating a stack for users that have a repo for multiple compose stacks..

Ah, I see and agree.

[lighterless]

I also have multiple stacks separated by folder in a single repo. It would be nice not only to be able to select the folder when deploying a stack from Git, but also to be able to POST a single webhook for an entire repo. This way whenever a repo file is updated, regardless of stack(s), the webhook call is made and Dockhand can update and deploy the relevant stack(s). That is how I have it setup in Komodo currently and it works quite nicely.

[ybizeul]

I also have multiple stacks separated by folder in a single repo. It would be nice not only to be able to select the folder when deploying a stack from Git, but also to be able to POST a single webhook for an entire repo. This way whenever a repo file is updated, regardless of stack(s), the webhook call is made and Dockhand can update and deploy the relevant stack(s). That is how I have it setup in Komodo currently and it works quite nicely.

I stumbled upon that issue for that exact use case, I think it deserves its own issue : #154

[thomaswienecke]

It would be great if this feature could have some form of autodiscovery mechanism. I guess this could work by configuring a regex path for compose-files in dockhand's UI or some form of .dockhand.yml config file in the repository which then could be read by dockhand.

My usage scenario would be to have a structure like @eximo84, but I'd love to be able to add new compose files without manually registering them in dockhand.

E.g. pushing a new commit with the Nginx service should be enough for dockhand to spin up the compose file.

REPO
|__ Applications
     |__ ...
     |__ Nginx
          |__ docker-compose.yaml
          |__ .env

[oblivioncth]

Aligned with the earlier comment: The docs already imply this is supported?

Multiple stacks can use the same Git repository with different compose paths. Each stack only redeploys when its own directory changes - commits to other directories are ignored.

[truthsword]

I too have multiple compose in my repo, but easily handled here:

[lgwapnitsky]

In Komodo, I have this option:

Something like this would be very handy in Dockhand