User's Nextcloud rollout already hit the classic trap of unprivileged-LXC
write attempts against an NFS share, so don't repeat that pattern for
Nexa. Updated docs to:
- Use SMB volumes mounted directly as docker volumes (driver: local,
type: cifs) with explicit username/uid/gid — bypasses LXC uid-mapping
entirely. Concrete YAML in docs/09 step 3 against
//192.168.1.31/nexa/<volume>.
- Keep the host-side /mnt/pve/unas NFS mount for admin-only use (rsync,
manual snapshot copies). Don't bind-mount it into containers.
- docs/12 #27 reordered to lead with SMB targets (qdrant, graphdb,
tei-cache, snapshots) and only mention NFS for host admin.
- CLAUDE.md storage block flipped to "SMB = default per-container
storage; NFS = host-side admin only".
- Also captured: deployments go through the Dockge UI (LXC is
the Dockge flavor of helper-scripts), not raw `docker compose up`.
- New optimization #30 about the local mail spool nag on the docker LXC
("You have new mail." at login).
Claude
a0a67eefab