# Grimmory on media-core

- LAN URL: `http://192.168.50.46:6060`
- Legacy evaluation library: `/mnt/truenas/multimedia/books` -> `/books` (read-only)
- Clean library projection: `/mnt/truenas/multimedia/grimmory/library` -> `/books-clean` (read-only)
- BookDrop: `/mnt/truenas/multimedia/grimmory/staging` -> `/bookdrop`
- Catalog snapshots and review reports: `/mnt/truenas/multimedia/grimmory/manifests`
- Rebuild state: `/opt/media-core/appdata/grimmory-rebuild/catalog.sqlite3`
- Application data: `/opt/media-core/appdata/grimmory/data`
- MariaDB data: `/opt/media-core/appdata/grimmory/mariadb`
- Storage mode: `NETWORK`

This is a parallel evaluation deployment. BookOrbit remains on the legacy
`/mnt/truenas/multimedia/books` tree, while Grimmory indexes a separately
materialized Work -> Edition -> Asset projection. Only Grimmory's dedicated
BookDrop is writable. Do not enable file rename, move, delete, or metadata
write-back against `/books` during the evaluation.

Keep the existing `Main Library` at `/books` until the clean projection has
been accepted. Create a second library at `/books-clean` with organization
mode `Book Per Folder`, metadata source `Prefer Sidecar`, and folder watching
disabled. Organization mode is immutable after library creation.

Set
`GRIMMORY_DB_PASSWORD` and `GRIMMORY_DB_ROOT_PASSWORD` only in the Arcane
project environment; do not commit their values.

Before an upgrade, dump the `grimmory` MariaDB database and back up
`/opt/media-core/appdata/grimmory/data`. Image tags describe the release and
the pinned OCI index digests are authoritative.