Grimmory (grimmory-tools/grimmory) is the community fork/successor of Booklore. Moving it off the shared apps LXC (105) onto a dedicated container (130, 192.168.8.213) to avoid the Portainer-managed stack footgun that wiped mariadb in April. - containers/130-grimmory.md: new container doc with compose layout, Authentik OIDC notes (PKCE/Public client), media-GID setup - plans/2026-06-29-grimmory-migration.md: step-by-step runbook for DB dump/restore, LXC provisioning, Caddy cutover, Authentik update - inventory.yaml: add grimmory LXC 130 - containers/105-apps.md: remove Booklore section + hostname entry - containers/index.md: update 105 row; add 130 row - infrastructure/media-permissions.md: add LXC 130; update Booklore→Grimmory refs - README.md: update 105 row; add 130 row Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
6.4 KiB
Plan: Migrate Booklore → Grimmory (LXC 130)
Status: in-progress
Date: 2026-06-29
Goal: Replace Booklore on shared apps LXC 105 with Grimmory on a dedicated LXC 130. Grimmory is the community fork/successor of Booklore with the same database schema and port, so the migration is a near-drop-in swap.
Pre-flight checklist
- Note Booklore MariaDB credentials from Portainer compose on LXC 105 (
DATABASE_PASSWORD,MYSQL_ROOT_PASSWORD) - Confirm
/mnt/library/booksis readable on LXC 105 (ls /mnt/library/books | head)
Step 1 — Dump Booklore MariaDB
# On hubris — find the MariaDB container name
pct exec 105 -- docker ps --format '{{.Names}}' | grep -i maria
# Dump (replace <CONTAINER> and <PASSWORD> from Portainer compose)
pct exec 105 -- docker exec <CONTAINER> \
mysqldump -u grimmory -p<PASSWORD> grimmory \
> /tmp/booklore-$(date +%Y%m%d).sql
# Pull to hubris root for safekeeping
pct pull 105 /tmp/booklore-$(date +%Y%m%d).sql /root/
Step 2 — Create LXC 130
# On hubris — list available Debian 13 templates
pveam list local | grep debian-13
# Create LXC
pct create 130 local:vztmpl/debian-13-standard_13.0-1_amd64.tar.zst \
--hostname grimmory \
--ostype debian \
--unprivileged 0 \
--cores 1 --memory 2048 --rootfs local-lvm:16 \
--net0 name=eth0,bridge=vmbr0,ip=dhcp \
--onboot 1 \
--mp0 /mnt/library,mp=/mnt/library \
--features nesting=1
pct start 130
pct exec 130 -- apt-get update -qq
Get the MAC address for the DHCP reservation:
pct config 130 | grep hwaddr
→ Add static DHCP lease 192.168.8.213 for this MAC on the Fritz!Box.
Step 3 — Bootstrap LXC 130
pct exec 130 -- bash -c '
# Media group
groupadd -g 10000 media
# Docker
apt-get install -y ca-certificates curl
curl -fsSL https://get.docker.com | sh
systemctl enable --now docker
'
Step 4 — Deploy Grimmory compose
pct exec 130 -- mkdir -p /opt/grimmory/mariadb/config /opt/grimmory/data /opt/grimmory/bookdrop
Write /opt/grimmory/docker-compose.yml on LXC 130:
services:
grimmory:
image: ghcr.io/grimmory-tools/grimmory:latest
container_name: grimmory
restart: unless-stopped
ports:
- "192.168.8.213:6060:6060"
volumes:
- ./data:/app/data
- /mnt/library/books:/books
- ./bookdrop:/bookdrop
environment:
- DATABASE_URL=jdbc:mariadb://mariadb:3306/grimmory
- DATABASE_USERNAME=grimmory
- DATABASE_PASSWORD=${GRIMMORY_DB_PASSWORD}
- USER_ID=0
- GROUP_ID=10000
- TZ=Europe/Berlin
- FORCE_DISABLE_OIDC=false
extra_hosts:
- "auth.hubris.network:192.168.8.175"
depends_on:
mariadb:
condition: service_healthy
mariadb:
image: lscr.io/linuxserver/mariadb:11.4.8
container_name: grimmory-mariadb
restart: unless-stopped
volumes:
- ./mariadb/config:/config
environment:
- MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
- MYSQL_DATABASE=grimmory
- MYSQL_USER=grimmory
- MYSQL_PASSWORD=${GRIMMORY_DB_PASSWORD}
healthcheck:
test: ["CMD", "mysqladmin", "ping", "-h", "localhost"]
interval: 10s
timeout: 5s
retries: 5
Write /opt/grimmory/.env on LXC 130 (fill real passwords):
GRIMMORY_DB_PASSWORD=<same_password_as_booklore>
MYSQL_ROOT_PASSWORD=<root_password>
Start:
pct exec 130 -- bash -c 'cd /opt/grimmory && docker compose up -d mariadb'
# wait ~15s for MariaDB to init, then start grimmory
pct exec 130 -- bash -c 'cd /opt/grimmory && docker compose up -d'
Verify Grimmory responds (before DB restore — will show setup wizard):
curl -s -o /dev/null -w '%{http_code}' http://192.168.8.213:6060
# expect 200 or 302
Step 5 — Restore Booklore DB
# Stop Grimmory (keep MariaDB running)
pct exec 130 -- docker stop grimmory
# Copy dump to LXC 130
pct push 130 /root/booklore-$(date +%Y%m%d).sql /tmp/booklore.sql
# Restore (replace <PASSWORD>)
pct exec 130 -- docker exec -i grimmory-mariadb \
mysql -u grimmory -p<GRIMMORY_DB_PASSWORD> grimmory \
< /tmp/booklore.sql
# Restart Grimmory
pct exec 130 -- docker start grimmory
Verify books appear:
curl -s http://192.168.8.213:6060 | grep -i grimmory
Step 6 — Authentik OIDC update
In Authentik Admin UI (https://auth.hubris.network):
- Providers → find
Bookloreprovider - Edit:
- Name:
Grimmory - Client Type: Public (Grimmory uses PKCE — no secret needed)
- Redirect URIs:
https://books.hubris.network/oauth2-callback - Scopes: openid, profile, email, offline_access
- Back-channel logout URL:
http://192.168.8.213:6060/api/v1/auth/oidc/backchannel-logout
- Name:
- Note the Client ID and Application slug for Grimmory's OIDC settings
In Grimmory Admin UI (http://192.168.8.213:6060 → Settings → Authentication → OIDC):
- Issuer URI:
https://auth.hubris.network/application/o/<slug>/(trailing slash required!) - Client ID: (from Authentik)
- Client Secret: leave blank (PKCE)
- Click Test Connection — all checks should pass (container reaches Authentik via extra_hosts)
Step 7 — Caddy cutover
In the dtoro/caddy-conf repo, update books.hubris.network:
books.hubris.network {
reverse_proxy 192.168.8.213:6060
}
Git push → Caddy webhook auto-reloads (see caddy (121)).
Test:
curl -s -o /dev/null -w '%{http_code}\n' https://books.hubris.network
Step 8 — Enroll as homelab client
homelab client add grimmory --lan-ip 192.168.8.213
Commits the age_pubkey back to inventory.yaml.
Step 9 — Verify end-to-end
https://books.hubris.networkloads Grimmory- OIDC login via Authentik works
- Library books from
/mnt/library/booksare visible - Reading progress / metadata from Booklore is present
Step 10 — Decommission Booklore on LXC 105
- Portainer → navigate to the Booklore stack → Stop → Remove
- Keep the dump at
/root/booklore-<date>.sqlon hubris (or archive to/mnt/library/documents/)
Rollback
If something goes wrong before Caddy cutover: no user-visible impact, just shut down LXC 130.
If Caddy already cut over: revert the books.hubris.network block to 192.168.8.205:6060 and push. Booklore still running on LXC 105 until Portainer stack is removed.