Name stack folders by stack name (not stack ID)

[KES777]

Is your feature request related to a problem? Please describe.
#7018 (comment)

Describe the solution you'd like

Would be nice if folders named like: mail, powerdns. eg. names provided from compose file.

Describe alternatives you've considered
Even if stack was named by portainer, docker-compose file should be checked. Portainer could asks to rename stack by name from compose file

[jamescarppe]

Portainer can manage multiple environments from the one interface, and as such there may be multiple stacks across those environments with the same names. We use an internal ID to keep track of the stacks, and since the files in the portainer_data volume aren't really intended for direct access by users we use that same ID for the files related to those stacks.

While we could use the stack names and prefix with an environment name / ID, this assumes these values remain the same, and as mentioned above, with no direct access provided to users to this filesystem it hasn't been something we've considered as a high priority change.

[KES777]

As workaround portainer could setup $STACK_ROOT environment variable which will point to stack directory, eg. ~/data/portainer/compose/17 in my case.

[csakaszamok]

It would be nice if we could use named folder (at least optionally).
There would some benefits.

• not too easy find something among in numbered folders
• sometimes i want to turn a simple docker-compose based host to in a standalone selfhosted portainer (without agent, etc), and usually on the server there is a very similar structure: a folder that contains (a lot) subfolders with docker-compose.yaml files.
  So it would be great, if I just had to aim portainer/compose folder to the existing (named) folder structure and it worked immediatelly.

[pebes]

still waiting for that feature in 2024