Saving the compose.yaml in the app folder for better restoration

[CamelT0E]

You have created a very nice OS for Docker. However, I would like to suggest a few small changes.

The compose.yaml should, as is usual with Docker, be stored at the top level of the mount. This not only allows for the container data to be easily backed up, but also the stack configuration for the container itself. Manual exporting of the compose.yaml would no longer be necessary. This hierarchy is already predefined in Docker and is implemented in NAS systems like Synology. During a reinstallation, you would only need to select the path to the compose.yaml and start it. Everything would work again. You could also easily move folders and files from another system, since relative paths can also be used in the compose.yaml.

If an image or logo could then be selected from a folder, that would be better than referencing a web logo. It would be even better if, in addition to reading the compose.yaml, a logo.png or logo.jpg could be loaded automatically. Then, the compose.yaml, .env, logo.png, and the data folder would all be in one directory. Restoring and moving would not be a problem by simply backing up the app folder.

example of nextcloud:

These suggestions are based on Docker and should be implemented in that way.
I would be happy if this matter is discussed, or if a developer can comment on its feasibility.
Please keep going. The system has a lot of potential, especially to simplify Docker for beginners!