Where Does Pingvin Share Store Data?
Pingvin Share keeps uploads plus SQLite in a ./data bind with optional config.yaml, all beside compose.
Last updated
Pingvin Share stores everything in a ./data directory: the SQLite database plus uploaded files (images get their own public subfolder). An optional config.yaml beside compose switches administration to files.
S3 mode splits the pair: files go to the bucket while the db stays local, so back up the database regardless. Match PUID/PGID ownership on the data bind or uploads fail opaquely. Share links survive either backup half.
Where Pingvin Share stores this, by platform
./data (Pingvin Share bind: db + uploads)
./data with SQLite db plus uploads; config.yaml optional beside compose. S3 mode still needs the db. Fix bind ownership via PUID/PGID.
Frequently asked questions
How do I migrate Pingvin Share?
Copy the data folder (db plus uploads) and config.yaml to the new host, then bring up the same compose file. S3-backed installs only need the db.
How do I configure Pingvin Share as code?
Mount a config.yaml based on the example; the admin UI then goes read-only. Env vars and mounted YAML mix, with files winning documented slots.
Notice an outdated path? Let us know.