MajorWiki/MajorWiki-Deploy-Status.md

title, status, project, updated

title	status	project	updated
MajorWiki Deployment Status	deployed	MajorTwin	2026-03-11

MajorWiki Deployment Status

Status: Deployed ✅

URL: https://notes.majorshouse.com Host: majorlab (/opt/majwiki) Port: 8092 (internal), proxied via Caddy Engine: MkDocs Material (squidfunk/mkdocs-material)

Stack

• Docker Compose at /opt/majwiki/compose.yml
• network_mode: host — container binds directly to host network
• MkDocs serves on 0.0.0.0:8092
• Caddy proxies notes.majorshouse.com → :8092
• Let's Encrypt cert provisioned 2026-03-11, valid until 2026-06-09

Why notes.majorshouse.com

wiki.majorshouse.com was provisioned and configured correctly but Google Fiber blocks TLS handshakes for SNI hostnames containing "wiki" at the ISP level. notes.majorshouse.com works fine on the same IP and port. wiki.majorshouse.com DNS record and Caddy entry have been removed.

Content

• 15 articles across 4 domains
• Source of truth: MajorVault/20-Projects/MajorTwin/08-Wiki/
• Deployed via rsync from MajorRig WSL2

Update Workflow

# From MajorRig (majorlinux user)
rsync -av --include="*.md" --include="*/" --exclude="*" \
  /mnt/c/Users/majli/Documents/MajorVault/20-Projects/MajorTwin/08-Wiki/ \
  root@majorlab:/opt/majwiki/docs/

# MkDocs hot-reloads automatically — no container restart needed

Backlog

• [✅] Gitea webhook for auto-deploy on push (Active as of 2026-03-11)
• Add 03-opensource and 05-troubleshooting articles (Troubleshooting seeded)

Incident Log

2026-03-11 — 502 Error & Webhook Repair

• Issue: Wiki returned 502 Bad Gateway.
• Cause: majwiki container was in a restart loop due to a LiterateNavParseError in SUMMARY.md (invalid globbing syntax).
• Repair: Rewrote SUMMARY.md with explicit links. Repaired majwiki-webhook.service by killing an orphaned process and correcting the Caddy reverse proxy routing for /webhook.
• Result: Site live and auto-deployment functional.