Where Does copyparty Store Config and Volumes?
copyparty reads its config file and serves volumes you choose at startup, so both live wherever you put them, not in fixed paths.
Last updated
copyparty has no fixed data directory by design. The config file (accounts, volumes, permissions) and the served folders are flags you pass at launch: -c for config, -v for each volume. Docker users typically bind ./cfg and ./data for exactly this.
That freedom puts the burden on your startup files. Version the compose file or service unit alongside the config so the paths stay documented. Back up volumes as plain files; nothing is ever locked inside a database.
Where copyparty stores this, by platform
./cfg (copyparty config bind, user-chosen)
Config and volumes live at flag-given paths (commonly ./cfg and ./data binds). Keep the compose or systemd unit with the config so mounts stay reproducible.
Frequently asked questions
How do I migrate copyparty to a new server?
Copy the config file and the volume folders to the new host, then adjust -v flags and user paths inside the config. Accounts and permissions travel in the config itself.
Why does copyparty forget settings in Docker?
Give the container or process a stable config path and matching volume mounts first. Ephemeral container filesystems otherwise discard every change on restart.
Notice an outdated path? Let us know.