1# Copyparty administration
2
3Snow Globe's Shares page manages native public links and separate API
4accounts. A person's page assigns folder permissions. Existing Copyparty
5permissions remain additive; changing a folder is an explicit retarget or move
6action. New shared folders default to `Share/Name - Description` under Clover.
7
8Copyparty owns its native `cfg/copyparty/shares.db` and selected-file records.
9`cfg/manager.json` stores API account labels, UUID-based folder grants, and link
10labels. API password hashes live in the service's Nomad variable under
11`file_api_<UUID without hyphens>`. Restore these together; restoring only the
12config file cannot recover managed accounts. `prepare.py` regenerates config
13from the canonical service policy and managed state on every deployment.
14
15A folder move must update the native share paths and selected-file records
16while Copyparty is stopped, preserving keys, passwords, permissions, expirations,
17and selected files. Code rollback does not undo filesystem moves. Rehearse on
18clones, retain restricted database/config backups, and verify the original
19public links after restart. The completed six-folder move's recovery evidence
20remains at `/var/lib/snowglobe/copyparty-cutover/20261016T082910Z-424b5410`.
21
22The privileged host unit reaches Copyparty through Podman's declared bridge
23subnet. A loopback-only network allowlist prevents configuration reloads even
24when its destination is a loopback-forwarded container port. Keep the derived
25bridge access when changing host restrictions.