Add Calibre-Web infrastructure
This commit is contained in:
61
Brain.md
Normal file
61
Brain.md
Normal file
@@ -0,0 +1,61 @@
|
||||
# Calibre-Web Brain
|
||||
|
||||
Service: Calibre-Web / Books
|
||||
|
||||
Domain:
|
||||
|
||||
```text
|
||||
https://books.mischlabs.de
|
||||
```
|
||||
|
||||
Gitea target:
|
||||
|
||||
```text
|
||||
https://git.mischlabs.de/MrDiderot/CalibreWeb.git
|
||||
```
|
||||
|
||||
Current NAS state captured on 2026-05-21:
|
||||
|
||||
```text
|
||||
Container: calibre-web
|
||||
Image: lscr.io/linuxserver/calibre-web:latest
|
||||
Ports: 0.0.0.0:8083->8083/tcp, :::8083->8083/tcp
|
||||
Status: Up 4 days
|
||||
```
|
||||
|
||||
Mounts:
|
||||
|
||||
```text
|
||||
/volume1/calibreweb/data/books -> /books
|
||||
/volume1/calibreweb/data/config -> /config
|
||||
```
|
||||
|
||||
Environment:
|
||||
|
||||
```text
|
||||
TZ=Europe/Berlin
|
||||
PUID=1000
|
||||
PGID=1000
|
||||
```
|
||||
|
||||
Note: The live Compose file uses `PGID=${PGID:-10}`, but the inspected running container reported `PGID=1000`. This likely comes from the NAS `.env`. Preserve the NAS `.env` value when redeploying.
|
||||
|
||||
Compose path on NAS:
|
||||
|
||||
```text
|
||||
/volume2/docker/calibreweb/docker-compose.yml
|
||||
```
|
||||
|
||||
Decision:
|
||||
|
||||
- This is currently an infrastructure repository, not a custom app image repository.
|
||||
- Use the upstream image `lscr.io/linuxserver/calibre-web:latest`.
|
||||
- The universal Watchtower instance on the NAS can update this service directly.
|
||||
- Only add a Dockerfile and Gitea Actions workflow if custom image changes become necessary later.
|
||||
- The initial `docker-compose.yml` in this repo was copied from the live NAS compose file at `/volume2/docker/calibreweb/docker-compose.yml`.
|
||||
|
||||
Important:
|
||||
|
||||
- Do not move or delete `/volume1/calibreweb/data/books`.
|
||||
- Do not move or delete `/volume1/calibreweb/data/config`.
|
||||
- If Calibre-Web appears empty after deployment, check bind mounts before assuming data loss.
|
||||
Reference in New Issue
Block a user