🚀 Feature Request: Support for stacks in nested directories

[calrock27]

⚠️ Please verify that this feature request has NOT been suggested before.

• I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

As a user, I would like to be able to manage stacks that are nested inside other folders visible to Dockge... I currently organize a few of my compose files in sub folders of their use case. I'll provide an example below.

My existing folder structure -
/opt/stacks/game_services
->/satisfactory/docker-compose.yml
->/minecraft/docker-compose.yml

In it's current state, Dockge sees my /game_services directory as empty because it does not contain a compose file.

✔️ Solution

When clicking on the left hand side navigation for a folder stack, it would display a tree of directories and allow me to drill down to the compose file I'm looking to manage.

If a compose file does exist in the directory, it should display on the right hand side (current functionality) until I click into a sub directory, in which case the right hand side would then display the compose file from the subdirectory.

❓ Alternatives

As an alternative solution, I've considered consoplidating all of my compose files from the /game_services directory into a single compose file in the /game_services directory. This ends up being a bit messy though as I have a few other dependent services with each game server.

📝 Additional Context

No response

[Keyruu]

Please implement this. I have 20 stacks I want to manage and if I don't put those in a nested folder it well get messy really quick.

[s4msy]

On the other hand, sorting all compose files to a reliable order into a stack folder brought some clearness in my mess. Did this yesterday, and I am really exited about this project.

But I would agree, allowing one parent folder should be enough and dockge goes searching its way down though all subfolders for compose files is an enhancement.

[BluDood]

This would be great, either something like a configurable value for nesting limit, or just being able to specify multiple directories for compose files

[DaftBrit]

Plus one on this, I've got a few third party github repos that nest their compose files and dockge is fantastic for managing stacks. As an alternative to having dockge trawl subfolders is it possible to have symlinks work? We could then leave the git structure alone and just create a symlink in the stacks folder with the name for the stack.

[aliuq]

I really hope to be able to identify nested directories. Currently there are 70+ under my stacks