compile: first compile — 17 entities, 2 synthesis, all indexes rebuilt

Read all 62 source files (Dev: 37, Homelab: 22, Venture: 3, Reference: 0).

Entity pages created (17):
- Wiki/Reference: lovebug, jenny, sunnie, n8n, ob1, tailscale, authentik,
  traefik, cloudflare, obsidian, gitea, plant-based-southerner, claude-code,
  dispatch, docker
- Wiki/Homelab: proxmox
- Wiki/Dev: pbs-hub, herbydev

Synthesis pages created (2):
- Wiki/Homelab/homelab-ingress-stack — four-layer ingress model (Cloudflare +
  Traefik + Authentik + Tailscale); operational lessons from 10+ source files
- Wiki/Dev/ai-memory-architecture — three memory layers (wiki + OB1 + Dispatch
  context); ingest paths; harness-vs-model design decision

All 11 index pages rebuilt (Sources/Dev, Venture, Homelab, Reference, Sources
root; Wiki/Dev, Venture, Homelab, Reference, Wiki root; vault root index.md).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Travis Herbranson 2026-05-08 18:15:31 -04:00
parent 34a268d8dc
commit 7eb8d756d1
32 changed files with 1214 additions and 35 deletions

View File

@ -8,16 +8,50 @@ updated: 2026-05-08
# Dev — Sources
Project plans and session notes for the Dev domain.
Project plans and session notes for coding, AI/ML, tooling, and dev environment work.
## Active Projects
*Updated by compile loop.*
- [[Sources/Dev/instagram-automation-content-hub-plan|instagram-automation-content-hub-plan]] — master plan for PBS Instagram automation (Phases 15)
- [[Sources/Dev/content-hub-phase5-architecture|content-hub-phase5-architecture]] — merge pbs-api + Content Hub into Blueprint Flask app
- [[Sources/Dev/content-hub-phase5-planning|content-hub-phase5-planning]] — locked decisions for Content Hub Phase 5
- [[Sources/Dev/content-hub-database-schema|content-hub-database-schema]] — `pbs_hub` MySQL schema design
- [[Sources/Dev/instagram-reel-sync-phase4|instagram-reel-sync-phase4]] — three-tier reel detection system
- [[Sources/Dev/pbs-membership-loe1-phase3|pbs-membership-loe1-phase3]] — "The Garden" member area build-out
- [[Sources/Dev/pbs-membership-loe1-phase2-save-button|pbs-membership-loe1-phase2-save-button]] — JS save button + heart→Sunnie animation
- [[Sources/Dev/pbs-membership-loe1-recipe-saving|pbs-membership-loe1-recipe-saving]] — backend API for recipe saves
- [[Sources/Dev/pbs-woocommerce-store|pbs-woocommerce-store]] — WooCommerce cookbook store
- [[Sources/Dev/cloudflare-cache-strategy|cloudflare-cache-strategy]] — cookie bypass + n8n auto-purge strategy
- [[Sources/Dev/cloudflare-cache-warmer|cloudflare-cache-warmer]] — daily sitemap-based cache warming
- [[Sources/Dev/email-to-obsidian-automation|email-to-obsidian-automation]] — Gmail → n8n → vault pipeline
- [[Sources/Dev/second-brain|second-brain]] — LLM wiki pattern; pull→transcribe→extract→review→publish
- [[Sources/Dev/wiki-vault-migration|wiki-vault-migration]] — vault consolidation from pbs-projects + homelab-projects
- [[Sources/Dev/herbys-dev-setup|herbys-dev-setup]] — herbydev Ansible setup + Tailscale VNC
- [[Sources/Dev/pbs-seo-automation|pbs-seo-automation]] — Google Search Console + Claude API meta generation
- [[Sources/Dev/pbs-youtube-analytics|pbs-youtube-analytics]] — YouTube Analytics API + Streamlit dashboard
- [[Sources/Dev/pbsii-cicd-pipeline|pbsii-cicd-pipeline]] — GitHub Actions + self-hosted runner on ustest1
- [[Sources/Dev/ansible-container-deploy|ansible-container-deploy]] — tag-based Docker deploy via Ansible
- [[Sources/Dev/a-review|a-review]] — agent code review skill
- [[Sources/Dev/zero-check-pipeline|zero-check-pipeline]] — LLM validation gauntlet (gitleaks, ruff, semgrep)
- [[Sources/Dev/project-scaffolding-skill|project-scaffolding-skill]] — Claude Code scaffolding skill
- [[Sources/Dev/pre-commit-framework-migration|pre-commit-framework-migration]] — pre-commit framework adoption
- [[Sources/Dev/wordpress-log-monitor|wordpress-log-monitor]] — WordPress log parsing → MySQL → Streamlit
- [[Sources/Dev/work-index-dashboard|work-index-dashboard]] — FastAPI+HTMX dashboard joining vault + Trello
- [[Sources/Dev/pbs-project-tracking|pbs-project-tracking]] — GitHub Issues + Trello two-layer tracking
- [[Sources/Dev/session-notes-convention|session-notes-convention]] — structured session note format standard
## Recent Sessions
*Updated by compile loop.*
- [[Sources/Dev/ai-memory-architecture-research|ai-memory-architecture-research]] — OB1 architecture; harness vs model layers; pgvector
- [[Sources/Dev/cloudflare-cache-rules|cloudflare-cache-rules]] — last-match-wins rule ordering; cookie bypass fix
- [[Sources/Dev/email-obsidian-git-pipeline|email-obsidian-git-pipeline]] — Gmail → n8n → Gitea → vault pipeline built
- [[Sources/Dev/instagram-automation-session-notes|instagram-automation-session-notes]] — MySQL schema; "Great Lockout of 2026" workaround
- [[Sources/Dev/pbs-api-db-connection-fix|pbs-api-db-connection-fix]] — pool_pre_ping=True, pool_recycle=1800
## Completed Projects
*Updated by compile loop.*
- [[Sources/Dev/github-deploy-refactor|github-deploy-refactor]] — pbsdeploybot + SSH host alias pattern ✓
- [[Sources/Dev/mailerlite-classic-to-new-migration|mailerlite-classic-to-new-migration]] — MailerLite Classic→New migration ✓
- [[Sources/Dev/pbs-woocommerce-golive|pbs-woocommerce-golive]] — Stripe/PayPal live; VA tax registration ✓
- [[Sources/Dev/production-deploy-march-2026|production-deploy-march-2026]] — March 2026 production deploy ✓
- [[Sources/Dev/recipe-cards-seed-packets|recipe-cards-seed-packets]] — `[pbs_recipes]` shortcode + seed packet design ✓

View File

@ -8,16 +8,36 @@ updated: 2026-05-08
# Homelab — Sources
Project plans and session notes for the Homelab domain.
Project plans and session notes for infrastructure, networking, hardware, and deployments.
## Active Projects
*Updated by compile loop.*
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server (FastMCP + Authentik + Cloudflare Tunnel); Phase 1 tools
- [[Sources/Homelab/ob1-main-deployment|ob1-main-deployment]] — OB1 AI memory system (Supabase + pgvector); Phases 06
- [[Sources/Homelab/ob1-deployment|ob1-deployment]] — OB1 addendum: Tailscale-only, parallel n8n write, Phase 7 Dispatch hook
- [[Sources/Homelab/traefik-deployment|traefik-deployment]] — full Traefik ingress stack; Knot DNS; wildcard TLS; Cloudflare Tunnel
- [[Sources/Homelab/pbs-infrastructure-intelligence|pbs-infrastructure-intelligence]] — PBSII: Go collector + Python log parser + n8n monitor + Claude API healer
- [[Sources/Homelab/ssh-ca-with-step-ca-authentik|ssh-ca-with-step-ca-authentik]] — step-ca + Authentik OIDC for short-lived SSH certs
- [[Sources/Homelab/pbs-security-hardening|pbs-security-hardening]] — Crowdsec + Authelia layered security for PBS
- [[Sources/Homelab/hunyuan3d-sunnie-pipeline|hunyuan3d-sunnie-pipeline]] — Hunyuan3D-2 on RTX 3080; Blender + Mixamo for Sunnie 3D
- [[Sources/Homelab/instantmesh-docker|instantmesh-docker]] — InstantMesh Docker on Manjaro tower
- [[Sources/Homelab/cli-standardization|cli-standardization]] — Fish + Starship + Chezmoi dotfiles via Ansible
- [[Sources/Homelab/editor-stack-upgrade|editor-stack-upgrade]] — Zed + Neovim/LazyVim + Zellij
- [[Sources/Homelab/env-file-hardening|env-file-hardening]] — root:root 0600 .env files
- [[Sources/Homelab/sshkm-local-ssh-key-manager|sshkm-local-ssh-key-manager]] — Python CLI for SSH key lifecycle
- [[Sources/Homelab/ssh-login-alerting|ssh-login-alerting]] — journald tailer → n8n → Google Chat alerts
## Recent Sessions
*Updated by compile loop.*
- [[Sources/Homelab/2026-05-06-homelab-mcp-server-stand-up|2026-05-06-homelab-mcp-server-stand-up]] — first MCP server deployment; Authentik OAuth + Cloudflare Tunnel; `mcp.herbylab.dev`
- [[Sources/Homelab/2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment|2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment]] — VLAN chip→bridge VID alignment (VID 11 lab, VID 21 private)
- [[Sources/Homelab/dns-knot-pihole-end-to-end|dns-knot-pihole-end-to-end]] — Knot DNS + Pi-hole chain live; rebind protection fix; EDE 15 debugging
- [[Sources/Homelab/homelab-dns-decision|homelab-dns-decision]] — locked Knot DNS architecture; split-horizon `.herbylab.dev`
- [[Sources/Homelab/server-stability-and-security-hardening|server-stability-and-security-hardening]] — MySQL OOM fix; WordPress cap; Cloudflare Bot Fight Mode; Traefik v3.6.11
- [[Sources/Homelab/server-stability-mysql-oom|server-stability-mysql-oom]] — MySQL OOM investigation (earlier session)
## Completed Projects
*Updated by compile loop.*
- [[Sources/Homelab/ufw-docker-outage-fix|ufw-docker-outage-fix]] — UFW after.rules DOCKER-USER outbound rules fix ✓
- [[Sources/Homelab/wp-cron-supercronic-deploy|wp-cron-supercronic-deploy]] — WP-Cron disabled; Supercronic sidecar; Traefik block-wpcron ✓
- [[Sources/Homelab/2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment|2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment]] — VLAN renumber ✓

View File

@ -8,16 +8,16 @@ updated: 2026-05-08
# Reference — Sources
Project plans and session notes for the Reference domain.
Cross-domain project plans and session notes that don't fit a single domain.
## Active Projects
*Updated by compile loop.*
*No source files in Reference yet. Cross-domain entities are in [[Wiki/Reference/index|Wiki/Reference]].*
## Recent Sessions
*Updated by compile loop.*
*None yet.*
## Completed Projects
*Updated by compile loop.*
*None yet.*

View File

@ -8,16 +8,17 @@ updated: 2026-05-08
# Venture — Sources
Project plans and session notes for the Venture domain.
Project plans and session notes for the PBS business — content, brand, marketing, and revenue.
## Active Projects
*Updated by compile loop.*
*No active project-plan pages in Venture yet — business direction is captured in session notes below.*
## Recent Sessions
*Updated by compile loop.*
- [[Sources/Venture/offsite-full-summary|offsite-full-summary]] — 3-day business off-site; vision/mission locked; 12-month revenue roadmap; eCookbook→membership→courses
- [[Sources/Venture/offsite-day1-business-dev|offsite-day1-business-dev]] — Day 1 business development; audience definition; 4 messaging pillars
## Completed Projects
*Updated by compile loop.*
*None yet.*

View File

@ -8,19 +8,26 @@ updated: 2026-05-08
# Sources
All project plans and session notes across domains.
All project plans and session notes. 62 files across Dev, Venture, and Homelab domains.
## By Domain
- [[Sources/Dev/index|Dev]] — coding projects, dev environment, AI/ML, tooling
- [[Sources/Venture/index|Venture]] — PBS business, content, brand, marketing
- [[Sources/Homelab/index|Homelab]] — infrastructure, networking, deployments
- [[Sources/Reference/index|Reference]] — cross-domain reference notes
- [[Sources/Dev/index|Dev]] — 27 projects, 5 sessions — coding, AI/ML, tooling, PBS tech
- [[Sources/Venture/index|Venture]] — 0 projects, 2 sessions — PBS business, content, brand
- [[Sources/Homelab/index|Homelab]] — 14 projects, 8 sessions — infrastructure, networking, deployments
- [[Sources/Reference/index|Reference]] — (empty) cross-domain reference notes
## Active Projects
## Active Projects (cross-domain highlights)
*Updated by compile loop. See domain indexes for full listings.*
- [[Sources/Homelab/ob1-main-deployment|ob1-main-deployment]] — OB1 AI memory (Supabase + pgvector, Phases 06)
- [[Sources/Dev/instagram-automation-content-hub-plan|instagram-automation-content-hub-plan]] — PBS Instagram automation (Phases 15)
- [[Sources/Dev/pbs-membership-loe1-phase3|pbs-membership-loe1-phase3]] — The Garden membership area
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server for AI tool access
- [[Sources/Dev/second-brain|second-brain]] — LLM wiki + AI memory architecture
## Recent Sessions
## Recent Sessions (cross-domain highlights)
*Updated by compile loop.*
- [[Sources/Homelab/2026-05-06-homelab-mcp-server-stand-up|2026-05-06-homelab-mcp-server-stand-up]] — MCP server live at `mcp.herbylab.dev`
- [[Sources/Homelab/2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment|2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment]] — VLAN renumber complete
- [[Sources/Dev/ai-memory-architecture-research|ai-memory-architecture-research]] — OB1 architecture research
- [[Sources/Dev/email-obsidian-git-pipeline|email-obsidian-git-pipeline]] — email-to-vault pipeline live

View File

@ -0,0 +1,110 @@
---
type: synthesis
path: Wiki/Dev
tags:
- ob1
- embeddings
- pgvector
- wiki
- automation
- mcp
sources:
- "[[Sources/Dev/ai-memory-architecture-research]]"
- "[[Sources/Dev/second-brain]]"
- "[[Sources/Homelab/ob1-main-deployment]]"
- "[[Sources/Homelab/ob1-deployment]]"
- "[[Sources/Dev/email-to-obsidian-automation]]"
- "[[Sources/Dev/email-obsidian-git-pipeline]]"
- "[[Sources/Homelab/homelab-mcp-server]]"
- "[[Sources/Homelab/2026-05-06-homelab-mcp-server-stand-up]]"
- "[[Sources/Dev/wiki-vault-migration]]"
created: 2026-05-08
updated: 2026-05-08
---
# AI Memory Architecture
## Synthesis
Travis's AI memory system is not a single tool but a layered architecture: a structured wiki vault for human-readable knowledge, a pgvector semantic store for AI-queryable memory, a homelab MCP server to expose both to AI agents, and n8n pipelines to keep all layers in sync. These components appear across 8+ projects and represent a coherent long-term investment in AI-assisted knowledge work.
### The Three Memory Layers
```
Layer 1: Structured Wiki (wiki-vault)
- Human-readable Markdown
- Obsidian wikilinks + navigation
- Compiled by LLM (wiki-maintenance skill)
- Git-versioned
- Written by: MCP server, email pipeline, Travis/Jenny
Layer 2: Semantic Memory (OB1)
- Supabase + pgvector
- Embeddings of vault content + session context
- Queryable by AI agents via semantic search
- Written by: n8n parallel pipeline (mirrors vault writes)
- Access: Tailscale-only
Layer 3: Agent Context (Dispatch / Lovebug)
- Active working memory within Claude Code context windows
- Pre-compact hook (Phase 7) will drain important context → OB1
- MCP server provides tool access to query OB1 and wiki from active sessions
```
### Ingest Paths
Multiple input channels feed into the wiki-vault and, in parallel, into OB1:
1. **MCP server** (`mcp.herbylab.dev`) — Claude Code and other AI agents write session notes and project updates directly to `Sources/` via the MCP tools. This is the primary agentic write path.
2. **Email pipeline** — Gmail → n8n → Gitea push → vault. Designed for mobile/async capture: send an email, it becomes a session note. Built and validated in the email-obsidian-git-pipeline session.
3. **Manual / direct** — Travis or Jenny write directly to the vault via Obsidian.
4. **Parallel OB1 write** (planned) — n8n intercepts all vault writes and mirrors them to OB1 as embeddings. Not yet live; pending OB1 deployment Phase 4.
### Query Paths
- **Wiki** — humans browse via Obsidian; AI agents query via MCP vault-read tools
- **OB1** — AI agents query via MCP OB1-recall tools (semantic search over embeddings)
- **Context injection** — the homelab MCP server exposes both layers as Claude Code tools, enabling Lovebug to pull relevant wiki pages or OB1 memories as needed within a session
### Harness vs. Model Architecture
The AI memory research session explored the design question: should AI memory be implemented at the **model layer** (fine-tuning, RLHF on personal data) or the **harness layer** (RAG, context injection, external retrieval)? The conclusion was harness-layer: model weights are slow and expensive to update, while a pgvector store + MCP injection is fast, reversible, and inspectable. Poolside and Pi.dev were evaluated as examples of model-layer approaches — useful for code but not for personal episodic memory.
The two memory modes are distinct:
- **Episodic** (session notes, project logs) → OB1 embeddings for temporal/event recall
- **Semantic** (wiki entity pages, synthesis) → wiki-vault for stable structured knowledge
### The Second-Brain Pattern
The `second-brain` project captures the Karpathy LLM wiki pattern: pull raw content → transcribe → extract entities/facts → review → publish to wiki. This is exactly what the wiki-maintenance compile loop implements. The compile loop is the "review → publish" step; the MCP server + email pipeline are the "pull → capture" steps. OB1 adds the AI-queryable retrieval layer that the pure wiki-markdown model lacks.
### MCP Server as the Integration Point
The homelab MCP server (`mcp.herbylab.dev`, deployed 2026-05-06) is the critical integration point that makes this architecture operational. Before MCP, each layer was separate — the wiki was browsed in Obsidian, OB1 was planned but not integrated, and AI agents had no way to query either during a session. The MCP server exposes vault tools and (once OB1 is live) OB1 recall as Claude Code tool calls, making the entire memory stack available to Lovebug mid-session.
## Sources
**ai-memory-architecture-research** (session notes) provides the harness-vs-model architecture decision, the pgvector choice, and the Poolside/Pi.dev research. This is the foundational design session for OB1.
**second-brain** (project plan) captures the Karpathy LLM wiki pattern and maps it to the wiki-vault compile loop + MCP server design. Establishes the pull→transcribe→extract→review→publish pipeline.
**ob1-main-deployment** (project plan) provides the full OB1 deployment architecture: Supabase + pgvector, Phases 06, embedding pipeline design.
**ob1-deployment** (addendum) captures the locked decisions: Tailscale-only access, n8n parallel write pipeline, Phase 7 Dispatch pre-compact hook. Critical refinements to the main plan.
**email-to-obsidian-automation** and **email-obsidian-git-pipeline** document the Gmail → n8n → Gitea → vault ingest path. The pipeline is built and validated as of May 2026.
**homelab-mcp-server** and **2026-05-06-homelab-mcp-server-stand-up** document the MCP server deployment: FastMCP Streamable HTTP, Authentik OAuth2, Cloudflare Tunnel. The integration point connecting all memory layers to AI agents.
**wiki-vault-migration** documents the vault consolidation from pbs-projects + homelab-projects into this unified structure, establishing the wiki-vault as the canonical structured knowledge store.
## Open questions
- OB1 Phases 06 deployment timeline: what is the current blocker? The addendum was written but the deployment plan doesn't indicate Phase 0 is complete.
- When the n8n parallel write pipeline goes live, will it backfill existing vault content (all 62+ notes) into OB1, or only new writes going forward?
- The Dispatch pre-compact hook (Phase 7) depends on Dispatch exposing a lifecycle event. Is this a Dispatch feature that already exists, or does it require Dispatch development work?
- How will the MCP server's OB1 recall tool handle stale embeddings when vault content is updated by the compile loop? Will there be a re-embed step in the compile procedure?
- The wiki + OB1 parallel write model creates two sources of truth for the same content. Reconciliation strategy (wiki as authoritative; OB1 as derived index) should be documented once the pipeline goes live.

50
Wiki/Dev/herbydev.md Normal file
View File

@ -0,0 +1,50 @@
---
type: entity
path: Wiki/Dev
tags:
- homelab
- terminal
- ansible
created: 2026-05-08
updated: 2026-05-08
---
# herbydev
## What it is
herbydev is Travis's primary development workstation — a Proxmox VM that serves as the main environment for all coding, homelab management, and AI-assisted work. It was promoted from `us-test-authy` (renamed and reconfigured). herbydev is where Claude Code runs, where skills live, and where Ansible playbooks are executed. It has Tailscale for remote VNC access.
## Current state
Active. Setup highlights:
- **Shell** — Fish + Starship prompt (via cli-standardization project)
- **Dotfiles** — Chezmoi for dotfile management, applied via Ansible
- **Editor** — planned upgrade to Zed + Neovim/LazyVim + Zellij (editor-stack-upgrade project)
- **Claude Code** — installed; skills at `~/.claude/skills/`; MCP server configured
- **Tailscale** — installed; VNC accessible remotely
- **Ansible** — Ansible playbook governs full herbydev setup
- **GitHub Actions** — ustest1 (separate Proxmox VM) hosts the self-hosted runner, but herbydev is the dev origin
## Where it lives
- Proxmox VM in homelab
- Accessible via Tailscale VPN (VNC)
- Domain: `herbydev.herbylab.dev` (split-horizon DNS)
## Related projects
- [[Sources/Dev/herbys-dev-setup|herbys-dev-setup]] — herbydev setup and promotion from us-test-authy
- [[Sources/Homelab/cli-standardization|cli-standardization]] — Fish + Starship + Chezmoi
- [[Sources/Homelab/editor-stack-upgrade|editor-stack-upgrade]] — Zed + Neovim + Zellij
- [[Sources/Dev/pbsii-cicd-pipeline|pbsii-cicd-pipeline]] — ustest1 runner (related VM)
- [[Wiki/Homelab/proxmox|proxmox]] — hypervisor
- [[Wiki/Reference/tailscale|tailscale]] — remote access
- [[Wiki/Reference/claude-code|claude-code]] — runs here
## History
- **2026** — Promoted from `us-test-authy`; Ansible playbook written for setup
- **2026** — Fish + Starship + Chezmoi standardized as shell stack
- **2026** — Claude Code installed; wiki-maintenance and other skills configured
- **2026-05-06** — MCP server at `mcp.herbylab.dev` added to Claude Code config

View File

@ -12,8 +12,9 @@ Compiled entities, topic landings, and synthesis for the Dev domain.
## Entities
*Updated by compile loop.*
- [[Wiki/Dev/pbs-hub|pbs-hub]] — Python Flask app merging pbs-api + Content Hub; Blueprint architecture; `pbs_hub` MySQL DB
- [[Wiki/Dev/herbydev|herbydev]] — Travis's primary dev workstation (Proxmox VM); Fish + Starship; Claude Code; Tailscale VNC
## Synthesis Pages
*Updated by compile loop.*
- [[Wiki/Dev/ai-memory-architecture|ai-memory-architecture]] — OB1 + wiki-vault + second-brain + MCP server; three memory layers; ingest and query paths

51
Wiki/Dev/pbs-hub.md Normal file
View File

@ -0,0 +1,51 @@
---
type: entity
path: Wiki/Dev
tags:
- pbs
- python
created: 2026-05-08
updated: 2026-05-08
---
# pbs-hub
## What it is
pbs-hub is the Python Flask application that consolidates two previously separate services — `pbs-api` and the Content Hub — into a single unified backend for Plant Based Southerner. It provides the API layer for the membership platform (recipe saving, member authentication), the Instagram automation pipeline, and content management. The Blueprint architecture allows modular feature ownership without a full microservices split.
## Current state
In active development (Phase 5 of Content Hub). Architecture decisions locked:
- **Blueprint structure** — each major feature area (recipes, membership, instagram, content) is a Flask Blueprint
- **Database**`pbs_hub` MySQL DB with tables: `projects`, `platform_posts`, `pbs_recipes`
- **Auth** — WordPress cookie-based auth for logged-in member verification
- **Recipe saving** — backend API for The Garden membership saves recipes via `pbs_hub` DB
Phase 5 merges `pbs-api` + Content Hub codebases. Prior phases (14) built the Instagram automation database schema ("Great Lockout of 2026" workaround), reel detection system, and content tracking.
## Where it lives
- PBS Linode Docker stack (`pbs-hub` service)
- Behind Traefik ingress
- Git: PBS project repo (Gitea + GitHub)
- DB: `pbs_hub` on shared MySQL instance in PBS stack
## Related projects
- [[Sources/Dev/content-hub-phase5-architecture|content-hub-phase5-architecture]] — Phase 5 merge plan
- [[Sources/Dev/content-hub-phase5-planning|content-hub-phase5-planning]] — planning decisions
- [[Sources/Dev/content-hub-database-schema|content-hub-database-schema]] — DB schema
- [[Sources/Dev/pbs-membership-loe1-recipe-saving|pbs-membership-loe1-recipe-saving]] — recipe save API
- [[Sources/Dev/instagram-automation-content-hub-plan|instagram-automation-content-hub-plan]] — master automation plan
- [[Sources/Dev/instagram-automation-session-notes|instagram-automation-session-notes]] — schema created
- [[Sources/Dev/instagram-reel-sync-phase4|instagram-reel-sync-phase4]] — reel detection system
- [[Sources/Dev/pbs-api-db-connection-fix|pbs-api-db-connection-fix]] — pool_pre_ping connection fix
- [[Wiki/Reference/plant-based-southerner|plant-based-southerner]] — parent entity
## History
- **2026** — MySQL schema created for Instagram automation; "Great Lockout of 2026" workaround implemented
- **2026** — Three-tier reel detection system designed (Phase 4)
- **2026** — DB connection fix: `pool_pre_ping=True`, `pool_recycle=1800`
- **2026** — Phase 5 architecture planned: merge pbs-api + Content Hub into Blueprint Flask app

View File

@ -0,0 +1,94 @@
---
type: synthesis
path: Wiki/Homelab
tags:
- traefik
- cloudflare
- authentik
- homelab
- networking
sources:
- "[[Sources/Homelab/traefik-deployment]]"
- "[[Sources/Homelab/homelab-mcp-server]]"
- "[[Sources/Homelab/2026-05-06-homelab-mcp-server-stand-up]]"
- "[[Sources/Dev/cloudflare-cache-strategy]]"
- "[[Sources/Dev/cloudflare-cache-rules]]"
- "[[Sources/Homelab/dns-knot-pihole-end-to-end]]"
- "[[Sources/Homelab/homelab-dns-decision]]"
- "[[Sources/Homelab/server-stability-and-security-hardening]]"
- "[[Sources/Homelab/wp-cron-supercronic-deploy]]"
- "[[Sources/Homelab/ufw-docker-outage-fix]]"
- "[[Sources/Homelab/pbs-security-hardening]]"
- "[[Sources/Homelab/ssh-ca-with-step-ca-authentik]]"
created: 2026-05-08
updated: 2026-05-08
---
# Homelab Ingress Stack
## Synthesis
The ingress architecture across both PBS and homelab converges on a layered pattern: Cloudflare at the edge, Traefik as the origin ingress, Authentik as the identity gate, and Tailscale as the private mesh. These four components appear together across 10+ project plans and session notes and form a coherent security + routing philosophy.
### The Four-Layer Model
```
Internet
└── Cloudflare (DNS + CDN + DDoS + Tunnel)
└── Traefik (TLS termination + routing + middleware)
└── Authentik (SSO/OAuth2/OIDC gate)
└── Service (WordPress, n8n, MCP server, etc.)
Private (Tailscale)
└── Direct service access (OB1, herbydev VNC, inter-service)
```
**Layer 1: Cloudflare** handles all public-facing concerns — authoritative DNS for both `plantbasedsoutherner.com` and `herbylab.dev`, CDN caching, DDoS/Bot Fight Mode, and zero-trust tunnel exposure (`cloudflared`). The cache rules use last-match-wins ordering with cookie-based bypass for authenticated members. The Cloudflare Tunnel pattern means origin servers never open inbound ports for public traffic — the tunnel initiates outbound, and Cloudflare routes to it.
**Layer 2: Traefik** is the Swiss Army knife — TLS termination (Let's Encrypt + Cloudflare DNS challenge for wildcards), Docker service discovery via labels, custom middleware (e.g., `block-wpcron`). It runs in both PBS and homelab contexts. After the March 2026 v3.6.11 upgrade, Traefik is stable; the UFW outage (missing DOCKER-USER rules) revealed that Docker + UFW interaction requires explicit outbound allow rules in `after.rules`.
**Layer 3: Authentik** gates sensitive services behind SSO. The MCP server was the first homelab service deployed behind Authentik OAuth2 (May 2026). The SSH CA project (step-ca + Authentik OIDC) extends this pattern to SSH key lifecycle — short-lived certificates replacing long-lived keys. The PBS security hardening plan adds Authentik/Authelia + Crowdsec as a second layer in front of WordPress admin.
**Layer 4: Tailscale** provides the private path — for services that should never be public (OB1, inter-VM communication) and for admin access (herbydev VNC). Tailscale and Cloudflare Tunnel serve complementary roles: Tunnel for public-facing services, Tailscale for private mesh.
### PBS vs. Homelab Divergence
PBS infrastructure is primarily Cloudflare + Traefik (no Authentik currently — WordPress handles its own auth). Homelab is where Authentik lives. The convergence point is the MCP server, which uses all four layers: Cloudflare Tunnel for external access, Traefik for routing, Authentik for OAuth2, and Tailscale as an alternative access path.
### Operational Lessons
- **UFW + Docker**: Docker rewrites iptables in a way that bypasses UFW INPUT rules. The fix is explicit DOCKER-USER chain rules in `/etc/ufw/after.rules`. Missing these caused a production outage.
- **WP-Cron via Traefik**: WordPress's built-in cron fires on HTTP requests, which Traefik handles normally. The Supercronic sidecar + `block-wpcron` middleware pattern removes this unpredictability.
- **Cloudflare cache + cookies**: The last-match-wins rule ordering means the cookie-bypass rule must come after the broad cache rule. Getting this wrong served cached logged-in pages to guests.
- **DNS rebind protection**: The Knot + Pi-hole chain requires Pi-hole rebind protection disabled for `.herbylab.dev` split-horizon entries — EDE 15 errors were the symptom.
### Planned Additions
- **Crowdsec + Authelia** — additional security layer for PBS WordPress admin
- **step-ca** — short-lived SSH certificates issued via Authentik OIDC
- **PBSII (pbs-infrastructure-intelligence)** — Go collector + log parser + n8n monitor feeding Claude API healer for automated incident response
## Sources
**traefik-deployment** provides the canonical Traefik setup: Knot DNS primary/secondary integration, wildcard TLS via Cloudflare DNS challenge, Cloudflare Tunnel wiring, and Tailscale placement in the topology. This is the reference document for the ingress architecture.
**homelab-mcp-server** and **2026-05-06-homelab-mcp-server-stand-up** document the first service deployed using the full four-layer pattern: Cloudflare Tunnel + Traefik + Authentik OAuth2 for `mcp.herbylab.dev`. The stand-up session notes capture the FastMCP Streamable HTTP setup.
**cloudflare-cache-strategy** and **cloudflare-cache-rules** capture the PBS CDN layer: last-match-wins rule design, cookie-bypass implementation, and n8n auto-purge integration. The session notes document the debugging process that revealed the rule ordering issue.
**dns-knot-pihole-end-to-end** and **homelab-dns-decision** capture the DNS architecture decision: Knot DNS as primary with secondary replica, Pi-hole as resolver, split-horizon for `.herbylab.dev`. The session notes document the rebind protection + EDE 15 debugging.
**server-stability-and-security-hardening** covers the March 2026 hardening sprint: Traefik v3.6.11 upgrade, Bot Fight Mode, MySQL OOM fix (768MB cap), WordPress memory cap.
**ufw-docker-outage-fix** documents the UFW + Docker interaction that caused a production outage, and the fix via explicit DOCKER-USER chain rules.
**wp-cron-supercronic-deploy** documents replacing WP-Cron with a Supercronic sidecar + `block-wpcron` middleware.
**pbs-security-hardening** and **ssh-ca-with-step-ca-authentik** cover the planned security expansions: Crowdsec + Authelia for PBS, step-ca + OIDC for SSH.
## Open questions
- Will the homelab run a second Traefik instance or share the PBS Traefik? The traefik-deployment plan implies a homelab-specific instance but this isn't fully resolved.
- The PBSII intelligence layer (Go collector + Claude API healer) would sit at the meta layer above all of this — when does that project move from plan to active?
- Crowdsec integration: does it sit in front of Traefik (as middleware) or beside it? The pbs-security-hardening plan doesn't fully specify placement.
- As OB1 goes live, does it get a Cloudflare Tunnel path for external access, or remain Tailscale-only permanently?

View File

@ -12,8 +12,8 @@ Compiled entities, topic landings, and synthesis for the Homelab domain.
## Entities
*Updated by compile loop.*
- [[Wiki/Homelab/proxmox|proxmox]] — bare-metal hypervisor for homelab VMs and LXCs; hosts DNS stack, Authentik, OB1, ustest1
## Synthesis Pages
*Updated by compile loop.*
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — Traefik + Knot DNS + Authentik + Cloudflare Tunnel; four-layer ingress model; operational lessons

50
Wiki/Homelab/proxmox.md Normal file
View File

@ -0,0 +1,50 @@
---
type: entity
path: Wiki/Homelab
tags:
- proxmox
- homelab
created: 2026-05-08
updated: 2026-05-08
---
# Proxmox
## What it is
Proxmox VE is the bare-metal hypervisor running in the homelab, hosting virtual machines and LXC containers for all homelab services. It provides the compute substrate under Authentik, DNS stack (Knot + Pi-hole), OB1 (Supabase + pgvector), the GitHub Actions self-hosted runner (ustest1), and future services. Proxmox's VM/LXC flexibility allows mixing full VMs (for services needing kernel isolation) with lightweight LXCs (for simpler services).
## Current state
Active. Key guests running on Proxmox:
- **ustest1** — Self-hosted GitHub Actions runner for PBS CI/CD (`pbsii-cicd-pipeline`)
- **DNS stack** — Knot DNS primary + secondary, Pi-hole (split-horizon `.herbylab.dev`)
- **Authentik** — SSO/IdP for homelab services
- **OB1** — Supabase + pgvector memory system (deployment in progress)
- **herbydev** — Primary dev workstation VM (promoted from us-test-authy)
VLAN scheme renumbered in May 2026: VID 11 (lab network), VID 21 (private network); OpenWrt switch chip aligned to bridge VID assignment.
## Where it lives
- Physical homelab hardware (specific host/model not documented in sources)
- Managed via Proxmox web UI and CLI
- Network: OpenWrt VLAN-segmented switch, VLANs 11/21
## Related projects
- [[Sources/Homelab/ob1-main-deployment|ob1-main-deployment]] — OB1 Supabase on Proxmox
- [[Sources/Dev/herbys-dev-setup|herbys-dev-setup]] — herbydev VM setup
- [[Sources/Dev/pbsii-cicd-pipeline|pbsii-cicd-pipeline]] — ustest1 GitHub Actions runner
- [[Sources/Homelab/dns-knot-pihole-end-to-end|dns-knot-pihole-end-to-end]] — DNS stack on Proxmox
- [[Sources/Homelab/2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment|2026-05-08-homelab-vlan-renumber-switch-chip-to-bridge-alignment]] — VLAN renumber
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server (Proxmox-hosted)
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — synthesis
## History
- Ongoing — Core homelab compute platform
- **2026** — DNS stack deployed: Knot DNS + Pi-hole chain live
- **2026** — herbydev promoted from us-test-authy (Proxmox VM rename/reconfigure)
- **2026-05-06** — MCP server deployed on Proxmox behind Authentik + Cloudflare Tunnel
- **2026-05-08** — VLAN scheme renumbered (VID 11 lab, VID 21 private); switch chip → bridge alignment fixed

View File

@ -0,0 +1,46 @@
---
type: entity
path: Wiki/Reference
tags:
- authentik
- homelab
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Authentik
## What it is
Authentik is the self-hosted identity provider (IdP) and SSO platform for homelab services. It handles OAuth2 and OIDC flows, providing centralized authentication for internal tools without relying on external identity providers. In the homelab stack, Authentik acts as the authorization layer in front of sensitive services, including the MCP server and planned SSH CA integration.
## Current state
Active. Current integrations:
- **Homelab MCP server** — Authentik provides OAuth2 for the `mcp.herbylab.dev` Streamable HTTP endpoint; first deployed May 2026
- **SSH CA (planned)** — step-ca + Authentik OIDC for short-lived SSH certificates, replacing long-lived keys
- **PBS security hardening (planned)** — Authentik / Authelia as second authentication layer for PBS services alongside Crowdsec
## Where it lives
- Homelab — running as a Docker container or Proxmox LXC/VM
- Accessible internally and via Cloudflare Tunnel / Traefik ingress
- Domain: likely `auth.herbylab.dev` (split-horizon `.herbylab.dev`)
## Related projects
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — OAuth2 for MCP endpoint
- [[Sources/Homelab/2026-05-06-homelab-mcp-server-stand-up|2026-05-06-homelab-mcp-server-stand-up]] — MCP stand-up session
- [[Sources/Homelab/ssh-ca-with-step-ca-authentik|ssh-ca-with-step-ca-authentik]] — SSH CA integration
- [[Sources/Homelab/pbs-security-hardening|pbs-security-hardening]] — layered PBS security
- [[Wiki/Reference/traefik|traefik]] — ingress layer
- [[Wiki/Reference/cloudflare|cloudflare]] — tunnel/DNS layer
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — synthesis
## History
- Ongoing — Core SSO platform for homelab services
- **2026-05-06** — First MCP server deployed behind Authentik OAuth2
- **Planned** — step-ca OIDC integration for short-lived SSH certs
- **Planned** — PBS security hardening layer alongside Crowdsec

View File

@ -0,0 +1,50 @@
---
type: entity
path: Wiki/Reference
tags:
- claude-code
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Claude Code
## What it is
Claude Code is Anthropic's AI coding assistant CLI — the primary AI collaborator used across all PBS, homelab, and dev projects. It operates as an interactive terminal agent with tool access (file read/write, bash, search), skill system (reusable procedural prompts), and MCP server integration. In this stack, Claude Code runs via the Dispatch framework with Lovebug as the named agent instance. The wiki-vault compile loop, PBS automation skills, and project scaffolding all run through Claude Code.
## Current state
Active. Used extensively across:
- **Wiki maintenance** — this vault's compile and lint operations via `wiki-maintenance` skill
- **Code review** — a-review skill with Gemini CLI / Ollama backends as reviewer pool
- **Scaffolding** — project-scaffolding-skill for Python, Go, and web project bootstrap
- **Validation** — zero-check pipeline (gitleaks, ruff, semgrep gauntlet before deploy)
- **PBS SEO** — Google Search Console data → Claude API → meta tag generation
- **Session-notes convention** — structured note format standardized for AI-assisted capture
- **MCP integration** — homelab MCP server (`mcp.herbylab.dev`) exposed as Claude Code tool source
## Where it lives
- CLI: installed on herbydev (and wherever Travis works)
- Skills: `~/.claude/skills/` on herbydev
- MCP servers: configured in Claude Code settings, including `mcp.herbylab.dev`
- Model: Claude Sonnet 4.6 (as of May 2026)
## Related projects
- [[Sources/Dev/a-review|a-review]] — code review skill
- [[Sources/Dev/zero-check-pipeline|zero-check-pipeline]] — pre-deploy validation
- [[Sources/Dev/project-scaffolding-skill|project-scaffolding-skill]] — project bootstrapping
- [[Sources/Dev/pbs-seo-automation|pbs-seo-automation]] — SEO meta generation
- [[Sources/Dev/wiki-vault-migration|wiki-vault-migration]] — vault migration
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP tool server
- [[Wiki/Reference/lovebug|lovebug]] — named agent instance
## History
- Ongoing — Primary AI coding tool across all projects
- **2026-05-08** — First wiki compile run; wiki-maintenance skill deployed
- **2026-05-06** — MCP server deployed; Claude Code can reach homelab tools
- **2026** — a-review, zero-check, scaffolding skills developed

View File

@ -0,0 +1,51 @@
---
type: entity
path: Wiki/Reference
tags:
- cloudflare
- homelab
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Cloudflare
## What it is
Cloudflare provides DNS, CDN caching, DDoS protection, and tunnel connectivity for PBS and homelab. All PBS traffic routes through Cloudflare before reaching the Linode origin server. Cloudflare Tunnel (formerly Argo Tunnel) is used to expose internal homelab services (MCP server, select homelab tools) to the internet without opening firewall ports on origin servers.
## Current state
Active across multiple roles:
- **DNS** — authoritative DNS for PBS domain and `herbylab.dev`
- **CDN caching** — cache rules tuned for PBS WordPress; last-match-wins rule ordering; cookie-based bypass for logged-in users
- **Bot Fight Mode** — enabled (added during March 2026 server stability hardening)
- **Cloudflare Tunnel** — homelab MCP server at `mcp.herbylab.dev` exposed via tunnel (no open inbound port)
- **Cache warming** — n8n daily sitemap crawl + cache purge pipeline (cloudflare-cache-warmer project)
- **Cache bypass fix** — cookie-based bypass ensures members see fresh content; n8n triggers purge on content publish
## Where it lives
- Cloudflare managed service (cloud-hosted control plane)
- `cloudflared` tunnel daemon runs on homelab/PBS Docker host
- n8n integration via Cloudflare API (cache purge webhook)
## Related projects
- [[Sources/Dev/cloudflare-cache-rules|cloudflare-cache-rules]] — cache rule configuration session
- [[Sources/Dev/cloudflare-cache-strategy|cloudflare-cache-strategy]] — cookie bypass + n8n purge strategy
- [[Sources/Dev/cloudflare-cache-warmer|cloudflare-cache-warmer]] — daily cache warming
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — tunnel for MCP server
- [[Sources/Homelab/server-stability-and-security-hardening|server-stability-and-security-hardening]] — Bot Fight Mode
- [[Wiki/Reference/traefik|traefik]] — origin ingress
- [[Wiki/Reference/n8n|n8n]] — cache purge automation
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — synthesis
## History
- Ongoing — Core DNS + CDN layer for PBS
- **2026** — Cache rule last-match-wins ordering locked; cookie bypass implemented
- **March 2026** — Bot Fight Mode enabled during server stability hardening
- **2026-05-06** — Cloudflare Tunnel deployed for MCP server at `mcp.herbylab.dev`
- **Planned** — Cache warming automation via n8n daily job

View File

@ -0,0 +1,38 @@
---
type: entity
path: Wiki/Reference
tags:
- dispatch
- claude-code
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Dispatch
## What it is
Dispatch is the AI agent orchestration and context management framework that manages Claude Code agent instances in this stack. It provides the lifecycle infrastructure for named agents like Lovebug — handling context windows, pre-compact hooks, session boundaries, and multi-turn agent coordination. A planned Phase 7 integration connects Dispatch's pre-compact lifecycle event to OB1 so that important context is persisted to memory before a context window is dropped.
## Current state
Active as the framework running Lovebug. The pre-compact → OB1 integration is planned (Phase 7 of OB1 deployment) but not yet implemented. The current setup uses Dispatch for agent invocation and Claude Code for tool execution, with the wiki-maintenance skill providing structured procedures.
## Where it lives
- Runs alongside Claude Code CLI on herbydev
- Configuration embedded in Claude Code / skill system
## Related projects
- [[Sources/Homelab/ob1-deployment|ob1-deployment]] — Phase 7 Dispatch pre-compact hook
- [[Sources/Dev/a-review|a-review]] — Dispatch-managed code review agent
- [[Wiki/Reference/lovebug|lovebug]] — primary named agent instance
- [[Wiki/Reference/ob1|ob1]] — memory system receiving pre-compact events
- [[Wiki/Reference/claude-code|claude-code]] — execution environment
## History
- Ongoing — Agent lifecycle framework for Lovebug
- **Planned** — Phase 7: Dispatch pre-compact hook writes context to OB1 before window drop

53
Wiki/Reference/docker.md Normal file
View File

@ -0,0 +1,53 @@
---
type: entity
path: Wiki/Reference
tags:
- docker
- homelab
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Docker
## What it is
Docker is the container runtime used across both PBS infrastructure and the homelab. In PBS, the entire application stack runs as Docker Compose services on the Linode server. In the homelab, Docker runs selected services on Proxmox LXCs or VMs. Docker provides environment isolation, reproducible deploys, and the foundation for the Ansible-based tag-driven deployment pipeline.
## Current state
Active. Two primary contexts:
**PBS Docker stack (Linode):**
- Services: WordPress, WooCommerce, n8n, pbs-hub (Flask), MySQL, Redis, Gitea, Supercronic, Traefik
- Deployment: Ansible `common/deploy.yml` with tag-based service targeting via `pbsdeploybot`
- CI/CD: GitHub Actions self-hosted runner on ustest1 triggers deploys
**Homelab Docker:**
- Services: Authentik, select homelab tools, MCP server, Hunyuan3D, InstantMesh
- Management: Ansible playbooks via herbydev
Security: `.env` files hardened to `root:root 0600`; `pbsdeploy` user cannot read secrets directly.
## Where it lives
- PBS: Linode VPS (Docker Engine + Docker Compose)
- Homelab: Proxmox LXCs/VMs running Docker Engine
## Related projects
- [[Sources/Dev/ansible-container-deploy|ansible-container-deploy]] — tag-based Ansible deploy pipeline
- [[Sources/Homelab/env-file-hardening|env-file-hardening]] — .env security hardening
- [[Sources/Dev/pbsii-cicd-pipeline|pbsii-cicd-pipeline]] — GitHub Actions CI/CD
- [[Sources/Dev/github-deploy-refactor|github-deploy-refactor]] — deploy user refactor
- [[Sources/Homelab/hunyuan3d-sunnie-pipeline|hunyuan3d-sunnie-pipeline]] — Docker for 3D pipeline
- [[Wiki/Reference/traefik|traefik]] — Docker service ingress
- [[Wiki/Reference/n8n|n8n]] — Docker service
## History
- Ongoing — Core container runtime for all services
- **2026** — Ansible tag-based deploy pipeline standardized
- **2026**`.env` hardening: `root:root 0600`, pbsdeploy access restricted
- **2026** — Supercronic added as WP-Cron replacement Docker sidecar

46
Wiki/Reference/gitea.md Normal file
View File

@ -0,0 +1,46 @@
---
type: entity
path: Wiki/Reference
tags:
- gitea
- git
- docker
created: 2026-05-08
updated: 2026-05-08
---
# Gitea
## What it is
Gitea is the self-hosted Git service running in the PBS Docker stack. It provides a private Git hosting layer for PBS projects, automation pipelines, and vault writes. Gitea hosts service accounts (like `pbsdeploybot`) used for CI/CD and automated git operations, keeping machine credentials separate from personal accounts.
## Current state
Active. Key roles:
- **pbsdeploybot machine user** — Gitea account used by GitHub Actions for PBS deployments; SSH host alias pattern avoids ambiguous key usage
- **Email-to-vault pipeline** — Gmail → n8n → Gitea push → vault (Gitea as the git push endpoint for new session notes)
- **Repository hosting** — hosts PBS-related private repos alongside GitHub mirrors
The GitHub deploy refactor project completed the migration to pbsdeploybot with Gitea SSH host aliases, replacing the previous ambiguous key setup.
## Where it lives
- PBS Linode Docker stack (`gitea` service)
- Behind Traefik ingress
- Persistent data in Docker volumes
## Related projects
- [[Sources/Dev/github-deploy-refactor|github-deploy-refactor]] — pbsdeploybot + SSH host alias pattern
- [[Sources/Dev/email-to-obsidian-automation|email-to-obsidian-automation]] — Gitea as vault write endpoint
- [[Sources/Dev/email-obsidian-git-pipeline|email-obsidian-git-pipeline]] — email pipeline session notes
- [[Sources/Dev/env-file-hardening|env-file-hardening]] — pbsdeploy credential separation
- [[Wiki/Reference/traefik|traefik]] — ingress layer
- [[Wiki/Reference/n8n|n8n]] — automation that pushes to Gitea
## History
- Ongoing — Self-hosted git service in PBS stack
- **2026** — pbsdeploybot machine user created; SSH host alias pattern implemented
- **2026** — Email-to-vault pipeline wired through Gitea as the push endpoint

View File

@ -12,8 +12,29 @@ Compiled entities, topic landings, and synthesis for the Reference domain.
## Entities
*Updated by compile loop.*
**People**
- [[Wiki/Reference/jenny|jenny]] — PBS co-founder and content creator; face of the brand
- [[Wiki/Reference/sunnie|sunnie]] — PBS mascot; sun character; "Sunnies" community name
**PBS Business**
- [[Wiki/Reference/plant-based-southerner|plant-based-southerner]] — plant-based cooking brand; WordPress/WooCommerce; active membership + store
**AI & Agents**
- [[Wiki/Reference/lovebug|lovebug]] — named AI coding agent; Dispatch instance; primary collaborator
- [[Wiki/Reference/ob1|ob1]] — AI memory system; Supabase + pgvector; Tailscale-only; Phases 06
- [[Wiki/Reference/claude-code|claude-code]] — Anthropic CLI; primary AI tool across all projects
- [[Wiki/Reference/dispatch|dispatch]] — AI agent orchestration framework; manages Lovebug lifecycle
**Automation & Infrastructure**
- [[Wiki/Reference/n8n|n8n]] — self-hosted workflow automation; central automation hub
- [[Wiki/Reference/traefik|traefik]] — reverse proxy and ingress router; PBS stack + homelab
- [[Wiki/Reference/cloudflare|cloudflare]] — DNS + CDN + DDoS + Tunnel; PBS and homelab edge
- [[Wiki/Reference/authentik|authentik]] — self-hosted SSO/IdP; OAuth2 + OIDC for homelab services
- [[Wiki/Reference/tailscale|tailscale]] — mesh VPN; private access for homelab and OB1
- [[Wiki/Reference/obsidian|obsidian]] — knowledge management app; this vault's browser
- [[Wiki/Reference/gitea|gitea]] — self-hosted git service; pbsdeploybot; vault write endpoint
- [[Wiki/Reference/docker|docker]] — container runtime; PBS stack + homelab services
## Synthesis Pages
*Updated by compile loop.*
*No Reference synthesis pages yet — cross-cutting analysis is in [[Wiki/Dev/ai-memory-architecture|Wiki/Dev]] and [[Wiki/Homelab/homelab-ingress-stack|Wiki/Homelab]].*

39
Wiki/Reference/jenny.md Normal file
View File

@ -0,0 +1,39 @@
---
type: entity
path: Wiki/Reference
tags:
- pbs
- venture
created: 2026-05-08
updated: 2026-05-08
---
# Jenny
## What it is
Jenny is Travis's partner and co-founder of Plant Based Southerner. She is the face of the brand and creates all food content — recipes, YouTube videos, Instagram Reels, and photography. Travis handles all technical infrastructure; Jenny drives the content strategy, brand voice, and audience relationships. The PBS brand is built around her personality and cooking style (plant-based Southern cooking accessible to families).
## Current state
Active. Currently producing recipes and video content. The 3-day off-site in early 2026 locked the PBS vision/mission, audience definition (busy women feeding families), and 12-month revenue roadmap. Near-term focus is on launching The Garden membership platform and growing the eCookbook catalog. Revenue target: $13k/month from membership and digital products. "Sunnies" is the name for the PBS community/audience.
## Where it lives
N/A — person, not a system. PBS business is at plantbasedsoutherner.com.
## Related projects
- [[Sources/Venture/offsite-full-summary|offsite-full-summary]] — 3-day off-site strategy sessions
- [[Sources/Venture/offsite-day1-business-dev|offsite-day1-business-dev]] — vision/mission/positioning
- [[Sources/Dev/pbs-membership-loe1-phase3|pbs-membership-loe1-phase3]] — The Garden member area
- [[Sources/Dev/pbs-woocommerce-golive|pbs-woocommerce-golive]] — eCookbook store go-live
- [[Sources/Dev/recipe-cards-seed-packets|recipe-cards-seed-packets]] — recipe card shortcode
- [[Wiki/Reference/plant-based-southerner|plant-based-southerner]] — PBS as a business entity
- [[Wiki/Reference/sunnie|sunnie]] — PBS mascot
## History
- **2026 (early)** — 3-day business off-site: locked vision, mission, audience, 4 messaging pillars, 12-month revenue roadmap
- **20252026** — WooCommerce eCookbook store launched with live Stripe/PayPal
- Ongoing — YouTube, Instagram, and recipe content production

43
Wiki/Reference/lovebug.md Normal file
View File

@ -0,0 +1,43 @@
---
type: entity
path: Wiki/Reference
tags:
- lovebug
- dispatch
- claude-code
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Lovebug
## What it is
Lovebug is Travis's named AI coding agent — a Dispatch-managed Claude instance that serves as the primary AI collaborator across dev and homelab projects. It operates within Claude Code and the Dispatch framework, handling code generation, review, migration, and agentic multi-step tasks. The name "lovebug" functions as both a handle tag in the vault and the identifier used in prompts and skill configs.
## Current state
Active. Lovebug is referenced across 10+ project plans and session notes as the executing agent. Used for the a-review code review skill, the zero-check validation pipeline, PBS SEO meta generation, project scaffolding, wiki compile, and this vault itself. A Dispatch pre-compact hook (Phase 7 of OB1 deployment) is planned to wire Lovebug's context cycles into the OB1 memory system.
## Where it lives
- Runs inside Claude Code CLI on herbydev
- Dispatch framework manages agent lifecycle and context
- Skill configs live at `~/.claude/skills/` on herbydev
- Wiki-maintenance skill: `~/.claude/skills/wiki-maintenance/`
## Related projects
- [[Sources/Dev/a-review|a-review]] — agent code review skill
- [[Sources/Dev/zero-check-pipeline|zero-check-pipeline]] — LLM validation gauntlet
- [[Sources/Dev/project-scaffolding-skill|project-scaffolding-skill]] — scaffolding automation
- [[Sources/Dev/wiki-vault-migration|wiki-vault-migration]] — this vault
- [[Sources/Homelab/ob1-deployment|ob1-deployment]] — Phase 7 Dispatch hook
- [[Wiki/Reference/ob1|ob1]] — planned memory integration
## History
- **2026-05-08** — First wiki compile run executed by Lovebug on `claude/reverent-sinoussi` branch
- Ongoing — Serves as primary agent across all PBS, homelab, and dev project work
- Planned — OB1 Phase 7 will connect Dispatch pre-compact events to OB1 memory ingestion

53
Wiki/Reference/n8n.md Normal file
View File

@ -0,0 +1,53 @@
---
type: entity
path: Wiki/Reference
tags:
- n8n
- automation
- docker
created: 2026-05-08
updated: 2026-05-08
---
# n8n
## What it is
n8n is the self-hosted workflow automation platform running as a Docker container in the PBS infrastructure stack. It serves as the central automation hub connecting external services (Gmail, Google Drive, Instagram, YouTube, Cloudflare, Supabase) with internal systems (WordPress, pbs-hub, the Obsidian vault, OB1). n8n handles event-driven pipelines, scheduled jobs, webhook receivers, and multi-step data flows that would otherwise require custom code.
## Current state
Active. Current and planned automation workflows include:
- **Email-to-vault pipeline** — Gmail → n8n → Gitea → Obsidian vault (session note ingestion)
- **Cloudflare cache warming** — Daily sitemap crawl + Cloudflare cache purge triggers
- **Instagram automation** — Reel detection webhook, content hub sync
- **OB1 parallel write** — n8n writes to both wiki-vault and OB1 simultaneously (planned)
- **WordPress log monitoring** — Log event alerts via n8n
- **SSH login alerting** — journald tailer → n8n → Google Chat
- **YouTube analytics** — YouTube API → n8n → Streamlit pipeline (planned)
- **PBS SEO automation** — Google Search Console data → Claude API → meta generation
## Where it lives
- PBS Linode Docker stack, behind Traefik ingress
- Accessible via Traefik routing (internal + possibly tunneled)
- Persistent data in Docker volume
## Related projects
- [[Sources/Dev/email-to-obsidian-automation|email-to-obsidian-automation]] — email pipeline project plan
- [[Sources/Dev/email-obsidian-git-pipeline|email-obsidian-git-pipeline]] — email pipeline session notes
- [[Sources/Dev/cloudflare-cache-warmer|cloudflare-cache-warmer]] — cache warming via n8n
- [[Sources/Dev/instagram-automation-session-notes|instagram-automation-session-notes]] — Instagram webhook
- [[Sources/Homelab/ob1-deployment|ob1-deployment]] — parallel wiki+OB1 write
- [[Sources/Homelab/ssh-login-alerting|ssh-login-alerting]] — login alerts
- [[Sources/Dev/pbs-youtube-analytics|pbs-youtube-analytics]] — YouTube analytics pipeline
- [[Wiki/Reference/traefik|traefik]] — ingress layer
- [[Wiki/Reference/ob1|ob1]] — memory integration
## History
- Ongoing — Central automation hub for PBS + homelab operations
- **2026** — Email-to-vault pipeline built and validated (session notes live)
- **2026** — OB1 parallel write pipeline planned as part of OB1 Phase 4+
- **2026** — SSH login alerting project initiated

51
Wiki/Reference/ob1.md Normal file
View File

@ -0,0 +1,51 @@
---
type: entity
path: Wiki/Reference
tags:
- ob1
- embeddings
- pgvector
- automation
created: 2026-05-08
updated: 2026-05-08
---
# OB1
## What it is
OB1 is Travis's personal AI memory and retrieval system — a Supabase + pgvector stack that stores embeddings of project notes, session logs, and vault content to enable semantic recall across AI conversations. Named as a reference to the "Old Ben" Kenobi archetype of a wise, reliable memory keeper. OB1 sits alongside the wiki-vault in the broader second-brain architecture: the vault provides structured human-readable knowledge, OB1 provides fast semantic search for AI context injection.
## Current state
In active deployment across Phases 06. Key architectural decisions (from the addendum):
- **Tailscale-only access** — Phase 4 deferred public endpoint; OB1 only reachable over Tailscale mesh
- **Parallel write pipeline** — n8n writes new vault notes to both wiki-vault and OB1 simultaneously
- **Phase 7 (planned)** — Dispatch pre-compact hook wires Lovebug's context windows into OB1 for automatic memory ingestion before context is dropped
The AI memory architecture research session explored harness-vs-model layering, Poolside and Pi.dev approaches, and the split between episodic (session notes) and semantic (wiki entity) memory modes.
## Where it lives
- **Supabase instance** — hosted in homelab (Proxmox), contains pgvector extension
- **Ingest pipeline** — n8n on PBS Docker stack
- **Query interface** — planned: homelab MCP server exposes OB1 recall as a tool
- **Access** — Tailscale-only (no public endpoint)
## Related projects
- [[Sources/Homelab/ob1-main-deployment|ob1-main-deployment]] — full deployment plan (Phases 06)
- [[Sources/Homelab/ob1-deployment|ob1-deployment]] — addendum (Tailscale, parallel write, Phase 7)
- [[Sources/Dev/ai-memory-architecture-research|ai-memory-architecture-research]] — architecture research session
- [[Sources/Dev/second-brain|second-brain]] — wiki-vault + OB1 second-brain pattern
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server will expose OB1 recall
- [[Wiki/Reference/n8n|n8n]] — ingest pipeline
- [[Wiki/Reference/tailscale|tailscale]] — access layer
- [[Wiki/Dev/ai-memory-architecture|ai-memory-architecture]] — synthesis page
## History
- **2026** — Architecture research session: pgvector, harness vs model layers, Poolside/Pi.dev reviewed
- **2026** — Full deployment plan written (Phases 06, Supabase + pgvector)
- **2026** — Addendum locked: Tailscale-only, parallel n8n write, Phase 7 Dispatch hook
- **Planned** — MCP server integration to expose OB1 recall as homelab tool

View File

@ -0,0 +1,44 @@
---
type: entity
path: Wiki/Reference
tags:
- obsidian
- wiki
- automation
created: 2026-05-08
updated: 2026-05-08
---
# Obsidian
## What it is
Obsidian is the knowledge management application used to browse and edit this vault. It renders the wiki-vault as an interconnected graph of Markdown notes, resolving `[[wikilinks]]` into navigable links. This vault (`wiki-vault`) is an Obsidian vault — the file structure, frontmatter conventions, and wikilink syntax are all Obsidian-native. The homelab MCP server writes new session notes and project plans directly into the vault in Obsidian-compatible format.
## Current state
Active. The wiki-vault was migrated from `pbs-projects` and `homelab-projects` in May 2026 into this unified vault. The compile loop (wiki-maintenance skill) generates and maintains the Wiki/ layer. The MCP server at `mcp.herbylab.dev` writes directly to `Sources/` using Obsidian-compatible Markdown. The email-to-vault pipeline (Gmail → n8n → Gitea → vault) also writes to `Sources/`.
## Where it lives
- App: installed on herbydev (and likely Travis's personal machine)
- Vault: `/opt/projects/wiki-vault` on herbydev
- Git-backed: vault is a git repo, changes committed via git
- MCP server writes via Gitea/git push to vault repo
## Related projects
- [[Sources/Dev/wiki-vault-migration|wiki-vault-migration]] — vault migration project plan
- [[Sources/Dev/second-brain|second-brain]] — LLM wiki pattern (Karpathy)
- [[Sources/Dev/email-to-obsidian-automation|email-to-obsidian-automation]] — email pipeline to vault
- [[Sources/Dev/email-obsidian-git-pipeline|email-obsidian-git-pipeline]] — email pipeline session
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server writes to vault
- [[Wiki/Reference/ob1|ob1]] — parallel AI memory system
- [[Wiki/Dev/ai-memory-architecture|ai-memory-architecture]] — synthesis
## History
- **2026-05-08** — wiki-vault created, migrating pbs-projects and homelab-projects (62 notes)
- **2026** — Email-to-vault automation built (session notes ingested via Gmail → n8n pipeline)
- **2026-05-06** — MCP server deployed; writes session notes directly to vault
- **Planned** — n8n parallel write to both vault and OB1 on every new note

View File

@ -0,0 +1,53 @@
---
type: entity
path: Wiki/Reference
tags:
- pbs
- venture
- wordpress
created: 2026-05-08
updated: 2026-05-08
---
# Plant Based Southerner
## What it is
Plant Based Southerner (PBS) is Jenny's plant-based cooking content brand and business, with Travis handling all technical infrastructure. The brand centers on making plant-based versions of Southern cooking accessible to busy families — particularly women who want to feed their families healthier food without sacrificing flavor or time. Travis and Jenny run the business together, with Jenny as the content creator and face of the brand, and Travis as the sole engineer.
## Current state
Active and growing. Current state by area:
- **Website** — WordPress + WooCommerce on Linode Docker stack; Traefik ingress; Cloudflare CDN
- **Store** — WooCommerce eCookbook store live with Stripe + PayPal (went live 2025/early 2026); Virginia tax registration complete
- **Membership** — "The Garden" member area in active development; recipe saving feature (LOE1) across multiple phases; heart→Sunnie animation, seed-packet recipe cards
- **Email** — MailerLite (migrated Classic→New); custom Sunnie pop-up; "Sunnies" community name
- **Content** — YouTube channel, Instagram (Reels automation in progress), recipe content
- **Automation** — Instagram reel sync, content hub DB, n8n pipelines, YouTube analytics dashboard
- **Revenue roadmap** — eCookbooks → membership → courses; Jenny's target $13k/month from digital products
## Where it lives
- **Domain** — plantbasedsoutherner.com
- **Hosting** — Linode VPS, Docker Compose stack
- **Stack** — WordPress, WooCommerce, n8n, pbs-hub (Flask), MySQL, Redis, Gitea, Traefik, Cloudflare
## Related projects
- [[Sources/Venture/offsite-full-summary|offsite-full-summary]] — 3-day strategy off-site
- [[Sources/Dev/pbs-membership-loe1-phase3|pbs-membership-loe1-phase3]] — The Garden member area
- [[Sources/Dev/pbs-woocommerce-golive|pbs-woocommerce-golive]] — store go-live
- [[Sources/Dev/instagram-automation-content-hub-plan|instagram-automation-content-hub-plan]] — master automation plan
- [[Sources/Dev/content-hub-phase5-architecture|content-hub-phase5-architecture]] — pbs-hub architecture
- [[Wiki/Reference/jenny|jenny]] — co-founder
- [[Wiki/Reference/sunnie|sunnie]] — mascot
- [[Wiki/Dev/pbs-hub|pbs-hub]] — backend Flask app
## History
- Ongoing — Active content business
- **20252026** — WooCommerce store launched; Stripe/PayPal live; VA tax registration
- **2026 (early)** — 3-day off-site: vision/mission locked, 12-month revenue roadmap set
- **2026** — MailerLite Classic→New migration completed
- **2026** — The Garden membership platform in development
- **2026** — Instagram automation (Content Hub phases 15) in progress

47
Wiki/Reference/sunnie.md Normal file
View File

@ -0,0 +1,47 @@
---
type: entity
path: Wiki/Reference
tags:
- sunnie
- pbs
- venture
created: 2026-05-08
updated: 2026-05-08
---
# Sunnie
## What it is
Sunnie is the Plant Based Southerner mascot — a stylized sun character that embodies the PBS brand's warmth and energy. Sunnie appears in UI animations, email marketing, recipe cards, and is being developed as a 3D character for future content. "Sunnies" (plural) is the community name for PBS members and followers. Sunnie is both a visual brand asset and a cultural identifier for the audience.
## Current state
Active in branding across multiple touchpoints:
- **Membership UI** — heart-to-Sunnie animation on recipe save button (Phase 2 of membership LOE1)
- **Email marketing** — custom Sunnie pop-up designed for MailerLite Classic→New migration
- **Recipe cards** — seed-packet design aesthetic uses Sunnie branding
- **3D pipeline** — Hunyuan3D-2 + Blender + Mixamo pipeline in development for animated 3D Sunnie character; requires RTX 3080 for inference
## Where it lives
- Visual assets: PBS codebase and design files
- 3D pipeline: Manjaro tower (RTX 3080) via InstantMesh and Hunyuan3D Docker containers
- Membership platform: WordPress/pbs-hub via custom shortcodes and JS
## Related projects
- [[Sources/Dev/pbs-membership-loe1-phase2-save-button|pbs-membership-loe1-phase2-save-button]] — heart→Sunnie animation
- [[Sources/Dev/mailerlite-classic-to-new-migration|mailerlite-classic-to-new-migration]] — custom Sunnie pop-up
- [[Sources/Dev/recipe-cards-seed-packets|recipe-cards-seed-packets]] — seed packet design
- [[Sources/Homelab/hunyuan3d-sunnie-pipeline|hunyuan3d-sunnie-pipeline]] — 3D character pipeline
- [[Sources/Homelab/instantmesh-docker|instantmesh-docker]] — 3D mesh Docker setup
- [[Wiki/Reference/jenny|jenny]] — PBS content creator
- [[Wiki/Reference/plant-based-southerner|plant-based-southerner]] — PBS brand
## History
- **2026** — Heart→Sunnie save animation designed for The Garden membership area
- **2026** — Custom Sunnie pop-up created during MailerLite migration
- **2026** — Hunyuan3D-2 pipeline project started to create 3D animated Sunnie
- **2026** — Seed-packet recipe card design references Sunnie aesthetic

View File

@ -0,0 +1,46 @@
---
type: entity
path: Wiki/Reference
tags:
- tailscale
- homelab
- networking
created: 2026-05-08
updated: 2026-05-08
---
# Tailscale
## What it is
Tailscale is the WireGuard-based mesh VPN connecting Travis's homelab machines, development workstations, and cloud services into a unified private network. It provides zero-config encrypted connectivity without port forwarding or public exposure, making it the foundation for secure internal service access across the homelab and PBS infrastructure.
## Current state
Active mesh. Key usages:
- **herbydev access** — Tailscale enables VNC access to herbydev from anywhere
- **OB1 access** — OB1 (Supabase + pgvector) is Tailscale-only, no public endpoint
- **Homelab MCP server** — MCP access path includes Tailscale alongside Cloudflare Tunnel
- **Traefik deployment** — Tailscale listed as part of ingress topology (alongside Cloudflare Tunnel)
- **Cross-service auth** — Services that need inter-machine communication route over Tailscale
## Where it lives
- Installed on: herbydev, Proxmox hosts, PBS Linode server (where applicable), OB1 host
- Management: Tailscale admin console (cloud-hosted)
- No self-hosted control plane (using Tailscale's hosted coordination server)
## Related projects
- [[Sources/Dev/herbys-dev-setup|herbys-dev-setup]] — Tailscale VNC for herbydev
- [[Sources/Homelab/ob1-deployment|ob1-deployment]] — Tailscale-only OB1 access
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server access path
- [[Sources/Homelab/traefik-deployment|traefik-deployment]] — ingress topology includes Tailscale
- [[Wiki/Reference/cloudflare|cloudflare]] — complementary external access layer
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — synthesis
## History
- Ongoing — Foundational mesh VPN for all homelab connectivity
- **2026** — OB1 deployment locked as Tailscale-only (no public endpoint per addendum)
- **2026** — MCP server deployment uses Tailscale + Cloudflare Tunnel for dual access

52
Wiki/Reference/traefik.md Normal file
View File

@ -0,0 +1,52 @@
---
type: entity
path: Wiki/Reference
tags:
- traefik
- docker
- homelab
created: 2026-05-08
updated: 2026-05-08
---
# Traefik
## What it is
Traefik is the reverse proxy and ingress router for PBS infrastructure. It handles TLS termination, service routing, middleware chains, and integration with Cloudflare for DNS and tunnel-based access. Traefik runs as a Docker container in the PBS Linode stack and is the entry point for all HTTP/HTTPS traffic to PBS services.
## Current state
Active at version 3.6.11 (upgraded March 2026 during the server stability hardening session). Key configurations:
- **TLS** — wildcard certificates via Let's Encrypt + Cloudflare DNS challenge
- **Routing** — all PBS services (WordPress, n8n, pbs-hub, Gitea, MySQL proxy, etc.) routed through Traefik labels
- **Middleware**`block-wpcron` middleware prevents direct HTTP access to `wp-cron.php` (replaced by Supercronic sidecar)
- **Cloudflare Tunnel** — Traefik sits behind Cloudflare Tunnel for MCP and some homelab services
- **Knot DNS** — primary and secondary DNS integrated with Traefik TLS pipeline
The homelab also runs Traefik (or uses the same pattern) for `.herbylab.dev` services behind Authentik.
## Where it lives
- PBS Linode Docker stack (`traefik` service in Docker Compose)
- Config: labels on Docker Compose services + `traefik.yml` / `dynamic/` config files
- Homelab: separate Traefik instance (or shared) for `.herbylab.dev`
## Related projects
- [[Sources/Homelab/traefik-deployment|traefik-deployment]] — full Traefik deployment plan
- [[Sources/Homelab/server-stability-and-security-hardening|server-stability-and-security-hardening]] — v3.6.11 upgrade
- [[Sources/Homelab/wp-cron-supercronic-deploy|wp-cron-supercronic-deploy]] — block-wpcron middleware
- [[Sources/Homelab/ufw-docker-outage-fix|ufw-docker-outage-fix]] — UFW + Docker/Traefik outbound rules fix
- [[Sources/Homelab/homelab-mcp-server|homelab-mcp-server]] — MCP server behind Traefik
- [[Wiki/Reference/cloudflare|cloudflare]] — tunnel + DNS
- [[Wiki/Reference/authentik|authentik]] — auth layer
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — synthesis
## History
- Ongoing — Core PBS ingress layer
- **March 2026** — Upgraded to v3.6.11 during server stability work
- **March 2026**`block-wpcron` middleware added when Supercronic replaced WP-Cron
- **2026** — UFW `after.rules` fixed to restore Docker/Traefik outbound routing after UFW misconfiguration caused outage
- **2026-05-06** — Traefik used as ingress for MCP server at `mcp.herbylab.dev`

View File

@ -12,8 +12,8 @@ Compiled entities, topic landings, and synthesis for the Venture domain.
## Entities
*Updated by compile loop.*
*Venture-specific entities live in [[Wiki/Reference/index|Wiki/Reference]] as cross-domain entities (see [[Wiki/Reference/plant-based-southerner|plant-based-southerner]], [[Wiki/Reference/jenny|jenny]], [[Wiki/Reference/sunnie|sunnie]]).*
## Synthesis Pages
*Updated by compile loop.*
*None yet — Venture synthesis pages will cover content strategy, revenue model, and brand positioning as source material grows.*

View File

@ -20,8 +20,19 @@ Generated and maintained by the wiki-maintenance compile skill.
## Key Entities
*Updated by compile loop.*
- [[Wiki/Reference/lovebug|lovebug]] — named AI coding agent (Dispatch)
- [[Wiki/Reference/ob1|ob1]] — AI memory system (Supabase + pgvector)
- [[Wiki/Reference/plant-based-southerner|plant-based-southerner]] — the PBS business
- [[Wiki/Reference/jenny|jenny]] — PBS co-founder and content creator
- [[Wiki/Reference/n8n|n8n]] — central automation hub
- [[Wiki/Reference/traefik|traefik]] — reverse proxy + ingress
- [[Wiki/Reference/cloudflare|cloudflare]] — DNS + CDN + Tunnel edge
- [[Wiki/Reference/authentik|authentik]] — SSO/IdP
- [[Wiki/Dev/pbs-hub|pbs-hub]] — Flask backend for PBS
- [[Wiki/Homelab/proxmox|proxmox]] — homelab hypervisor
- *See domain indexes for full entity listings*
## Synthesis Pages
*Updated by compile loop.*
- [[Wiki/Dev/ai-memory-architecture|ai-memory-architecture]] — OB1 + wiki-vault + MCP; the full AI memory stack
- [[Wiki/Homelab/homelab-ingress-stack|homelab-ingress-stack]] — four-layer ingress: Cloudflare → Traefik → Authentik → Tailscale

View File

@ -3,6 +3,7 @@ type: topic-landing
tags:
- landing
updated: 2026-05-08
compiled: 2026-05-08
---
# Wiki Vault

16
log.md
View File

@ -8,3 +8,19 @@ Append-only event log. Each entry records a compile, lint, or migration run.
- Four domains: Dev, Venture, Homelab, Reference
- Migrated from pbs-projects and homelab-projects
- Notes: first entry, no prior compile history
## [2026-05-08] compile | first compile — 62 source files
- All 62 source files read (Dev: 37, Homelab: 22, Venture: 3, Reference: 0)
- Entity pages created: 17 total
- Wiki/Reference: lovebug, jenny, sunnie, n8n, ob1, tailscale, authentik, traefik,
cloudflare, obsidian, gitea, plant-based-southerner, claude-code, dispatch, docker (15)
- Wiki/Homelab: proxmox (1)
- Wiki/Dev: pbs-hub, herbydev (2)
- Synthesis pages created: 2
- Wiki/Homelab/homelab-ingress-stack — Traefik + Cloudflare + Authentik + Tailscale
- Wiki/Dev/ai-memory-architecture — OB1 + wiki-vault + MCP + Dispatch
- All index pages rebuilt: Sources/Dev, Sources/Venture, Sources/Homelab, Sources/Reference,
Sources/index, Wiki/Dev, Wiki/Venture, Wiki/Homelab, Wiki/Reference, Wiki/index, root index
- Entity promotions: all 17 met 2+ project threshold; Docker and Dispatch added per user spec
- No pages deleted or demoted