Currently, the image distributes persistence across multiple volumes (/config, /worlds, /logs, etc.), which can make organization on the host difficult.
My suggestion is to offer a variant (or option via environment variable) that uses only one user-mounted directory, for example, /data, and organize the structure within it:
/data
├── Config/ → configs (serverconfig.txt, etc.)
├── World/ → arquivos .wld
└── Log/ → logs do servidor
This would simplify management, facilitate backups, and prevent the creation of anonymous volumes when the user forgets to map all the necessary paths. The idea would be for the container to work the same way, but with all persistence centralized in a single user-defined folder.
Unfortunately, I don't have the technical expertise to make such an adjustment, but here's a suggestion in case anyone is thinking of something to contribute.
Currently, the image distributes persistence across multiple volumes (/config, /worlds, /logs, etc.), which can make organization on the host difficult.
My suggestion is to offer a variant (or option via environment variable) that uses only one user-mounted directory, for example, /data, and organize the structure within it:
/data
├── Config/ → configs (serverconfig.txt, etc.)
├── World/ → arquivos .wld
└── Log/ → logs do servidor
This would simplify management, facilitate backups, and prevent the creation of anonymous volumes when the user forgets to map all the necessary paths. The idea would be for the container to work the same way, but with all persistence centralized in a single user-defined folder.
Unfortunately, I don't have the technical expertise to make such an adjustment, but here's a suggestion in case anyone is thinking of something to contribute.