Record the working internal Gitea SSH remote as ssh://git@10.5.1.6:2222/<owner>/<repo>.git and replace stale HTTPS/gitea.paccoco.com examples for PD/NOMAD operations. Port 2222 is SSH, while the web UI remains on port 3002.
Document Paperless Tika/Gotenberg sidecars, supported Office/OpenDocument ingestion formats, stack paths, validation/deploy procedure, and verification commands. Updates service inventory and architecture overview so PD docs match the deployed documents stack.
Enable Paperless Office/OpenDocument ingestion by wiring internal Tika and Gotenberg services into the documents stack. Adds PAPERLESS_TIKA_* environment keys to .env.example and places both sidecars on an internal-only network with resource limits.
- 08-class-recording-rag-v1.1.json: Whisper URL → 10.5.1.16:8786,
model → faster-distil-whisper-small.en, auth headers → env vars,
inputDataFieldName fix, Paperless response format text
- PLAUSIBLEDENABILITY.md: remove Whisper from GPU list (moved to N.O.M.A.D.)
- n8n-workflows/README.md: fix class recordings path to /mnt/tank,
correct workflow 08 trigger (webhook, not folder watcher),
add curl upload example and docker-compose setup instructions
GITEA_HTTP_URL="http://10.5.1.6:3000"# ← local Gitea HTTP port (check TrueNAS app config)
GITEA_HTTP_URL="http://10.5.1.6:3000"# ← local Gitea HTTP port (check TrueNAS app config)
GITEA_SSH_PORT="2222"# ← Gitea SSH port
GITEA_SSH_PORT="2222"# ← Gitea SSH port
GITEA_USER="fizzlepoof"
GITEA_USER="fizzlepoof"
GITEA_TOKEN="aa711a194bd30f6355a0f5d396520d08762483aa"# ← regenerate with write:repository + write:user scopes
GITEA_TOKEN=""# ← set this before use; regenerate with write:repository + write:user scopes
REPO_NAME="homelab-secrets"
REPO_NAME="homelab-secrets"
LOCAL_PATH="/mnt/docker-ssd/docker/secrets"
LOCAL_PATH="/mnt/docker-ssd/docker/secrets"
KEY_EXPORT_PATH="/root/.git-crypt-secrets.key"# back this up somewhere safe!
KEY_EXPORT_PATH="/root/.git-crypt-secrets.key"# back this up somewhere safe!
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.