Where Does Photoview Store Photos and Database?
Photoview reads .env beside compose with photos at container photos path. Cache and DB choice follow env vars.
Last updated
Photoview splits into env file, database, media mount, and cache. The .env beside compose sets driver, passwords, and media roots. Photos mount readably at the container photos path, with each user rooted to a subpath. Face grouping tables join the same database file.
SQLite is the zero setup default with its file path in env. MariaDB and Postgres run as sibling services for bigger libraries. Thumbnail cache and face data derive from scans, so the DB plus env restore everything but the photos. User roots map to subpaths of one mount.
Where Photoview stores this, by platform
/opt/photoview/.env
Driver, passwords, and media roots. Copy from the example compose folder and chmod down. Rename from example names first.
/opt/photoview/photoview.db
SQLite file for default installs. Point the env var elsewhere to relocate. MariaDB users dump instead.
/opt/photoview/photos
Host photo library roots. Keep readable by others group or the scanner skips files. Never store DB here.
Frequently asked questions
How do I back up Photoview?
Back up .env, the database (sqlite file or dump), and note the photo roots. Photos themselves stay outside, so backup means config plus DB.
How do I point Photoview at my photos?
Set the photo path in initial setup to the container photos mount. Per user roots map to subfolders of the same mount.
Notice an outdated path? Let us know.