Add Grimmory evaluation stack for media-core
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
# Grimmory on media-core
|
||||
|
||||
- LAN URL: `http://192.168.50.46:6060`
|
||||
- Existing library: `/mnt/truenas/multimedia/books` -> `/books` (read-only)
|
||||
- BookDrop: `/mnt/truenas/multimedia/curator/staging/grimmory` -> `/bookdrop`
|
||||
- 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 online and both
|
||||
applications may index the same final library, but only Grimmory's dedicated
|
||||
BookDrop is writable. Do not enable file rename, move, delete, or metadata
|
||||
write-back against `/books` during the evaluation.
|
||||
|
||||
Create the first library at container path `/books`. 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.
|
||||
Reference in New Issue
Block a user