now that I was finally able to restart my seafile with V13 (THANKS daniel.pan), I noticed that on my test system, the folder shared contains now only a folder named seafile, the other folders such as nginx and logs are gone.
Since I use direct volume mapping to my host like this: Volume=/Storage/Seafile:/shared, the folders on my host are now /Storage/Seafile/seafile…
Would it be safe to use Volume=/Storage/Seafile:/shared/seafile as well? So that my host shows /Storage/Seafile? To avoid the nested folders? or do you plan to add new folders to /shared?
Kind regards,
Here is the analysis from our AI (manually checked)
The changes you are seeing in version 13.0 are part of a significant restructuring of the Docker deployment and how the internal Nginx handles configurations.
Directory Structure Changes
In Seafile v13, the internal organization has shifted to consolidate core data under /shared/seafile. This is the intended behavior of the new version. Additionally, the bundled Nginx in the Docker image no longer generates or reads configuration files from the mapped volume (like the old /shared/nginx folder); it is now used primarily for serving static files and internal proxying.
Is it safe to remap to /shared/seafile?
It is not recommended to change your volume mapping to /Storage/Seafile:/shared/seafile.
The Seafile container still expects /shared to be the root of its persistent data. Even if it looks like only one folder is there now, the startup scripts and internal components rely on the /shared path to manage various states, logs, and potential future component directories. If you map directly to /shared/seafile, the container may fail to initialize correctly because it cannot access or create the parent /shared structure it expects.
Summary
To ensure stability and compatibility with future updates, you should keep your mapping as Volume=/Storage/Seafile:/shared. While this creates a nested folder on your host, it ensures that all internal path references within the Seafile scripts remain valid.
If you are currently migrating, also keep in mind that many configurations have moved to environment variables in the .env file, and the old Nginx configuration directory is now obsolete.