Files
MajorWiki/MajorWiki-Deploy-Status.md

82 lines
2.7 KiB
Markdown

---
title: MajorWiki Deployment Status
status: deployed
project: MajorTwin
updated: '2026-03-12'
---
# 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
- 23 articles across 5 domains
- Source of truth: `MajorVault/20-Projects/MajorTwin/08-Wiki/`
- Deployed via Gitea webhook (push from MajorAir → auto-pull on majorlab)
## Update Workflow
```bash
# 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)
- [✅] Git repo initialized on MajorAir — push to deploy (2026-03-12)
- [✅] Troubleshooting section seeded with articles
- [ ] Add `03-opensource` articles
## 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.
---
*Updated 2026-03-13*
## Canonical Update Workflow
Obsidian Git plugin was evaluated and dropped — too convoluted. Manual git from the terminal is the workflow going forward.
```bash
cd ~/Documents/MajorVault
git add 20-Projects/MajorTwin/08-Wiki/
git commit -m "wiki: describe your changes"
git push
```
Gitea receives the push → fires webhook → majorlab pulls → MkDocs rebuilds → `notes.majorshouse.com` updates automatically.
> [!note] The rsync one-liner in the Update Workflow section above was a one-off during initial setup. It is no longer the canonical method.