copyparty wants a persistent volume for statefiles

[9001]

Hey!

Just watched the video, what a christmas present 😁

The ONLY thing I'd like to mention is that copyparty wants a volume to persistently store some state in, similar to tailscale's copyparty-ts-state. Currently, some features (mainly shares, user-changeable passwords, and filekeys/dirkeys) will only work as intended until the next time a --force-recreate is done, at which point they will "reset" and lose all settings.

By default, copyparty uses /cfg inside the container as the location for its statefiles -- this is specified by XDG_CONFIG_HOME -- and this folder is not currently a volume in the docker-compose.

I think the following is a good way to fix this; /cfg becomes a persistent volume, and the autogenerated /cfg/config.conf also seems to work (and update) as intended. But if you have better ideas then I'm all ears 👍

--- a/2025-12-copyparty/compose.yaml
+++ b/2025-12-copyparty/compose.yaml
@@ -47,8 +47,10 @@ services:
         target: /cfg/config.conf
     volumes:
       - copyparty-data:/data
+      - copyparty-state:/cfg
     restart: unless-stopped
 
 volumes:
   copyparty-ts-state:
+  copyparty-state:
   copyparty-data:

Merry xmas btw :>