Skip to content
FSS Knowledge Base

Web Deploy Pipeline Fixes

Section titled “Web Deploy Pipeline Fixes”

What was fixed

Section titled “What was fixed”

1. UAC prompt on desktop shortcut (June 17) Removed admin elevation from launch-web-deploy.bat and launch-web-deploy.ps1. Shortcut now runs without UAC. Admin rights only needed for LAN preview (right-click → Run as Administrator).

2. Stale PWA after deploy (June 17) Added @vite-pwa/astro with NetworkFirst navigation strategy, skipWaiting, and clientsClaim. Service worker now takes over immediately after each Cloudflare deploy.

3. Broken wikilinks on deployed sites (June 17) All Obsidian wikilinks were rendering as broken links. Created convert-wikilinks.ts for both kb-mbr and kb-business deploy pipelines. Handles \| table escapes, path-style targets, multi-vault prefixes. 95+ links fixed across both sites.

4. MBR deploy FATAL — homepage file not found (June 26) kb-mbr/sync-content.ts expected Strategy/00_KB Home.md. Phase 7 vault restructure moved it to MBR/DASHBOARD.md at root. Fixed: HOMEPAGE_FILENAME = 'DASHBOARD.md', HOMEPAGE_SOURCE_PATH = ''. Committed 0aab50c.

5. Core site silently failing Cloudflare builds (June 26) Root cause: Core/IT/Logs/Projects/monorepo/2026-06-25_review-reports/security.md used head: 9d9430f in frontmatter (a git commit hash). Astro/Starlight reserves head for injecting <head> HTML elements and expects an array — the string value broke schema validation. Cloudflare build failed silently; old deployment stayed live. Fix: renamed head: → commit: in the file.

6. Obsidian Bases blocks not rendering on deployed site (June 26) _DASHBOARD.md uses \“basequery blocks that only execute in Obsidian. On the deployed site they show as raw code. Createdkb-business/generate-bases.py`:

  • Runs as Step 2b in deploy.sh (after sync, before transform)
  • Scans all src/content/docs files for ```base ``` blocks
  • Matches each block to a query via preceding ## heading
  • Replaces with static markdown table (using wikilinks resolved by Step 3b)
  • Currently handles: All Active Tasks, Ready to Execute, By Risk Level, Blocked Tasks, Active Projects
  • Script moved from ~/utils/ai/kb_dashboard_gen.py; old script deleted

Files changed

Section titled “Files changed”
  • ~/utils/web/web-deploy/launch-web-deploy.bat — UAC fix
  • ~/utils/web/web-deploy/launch-web-deploy.ps1 — UAC fix
  • ~/utils/web/web-deploy/kb-mbr/sync-content.ts — homepage path fix
  • ~/utils/web/web-deploy/kb-mbr/deploy.sh — wikilink step added
  • ~/utils/web/web-deploy/kb-business/deploy.sh — wikilink + generate-bases steps
  • ~/utils/web/web-deploy/kb-business/generate-bases.py — new (moved from utils/ai/)
  • ~/utils/web/web-deploy/kb-business/README.md — Step 2b documented
  • Core/IT/Logs/Projects/monorepo/2026-06-25_review-reports/security.md — head: → commit:

Key gotcha

Section titled “Key gotcha”

Cloudflare build failures are invisible from deploy.sh — the script reports “Push complete!” on a successful git push even if the Cloudflare build fails. The old deployment stays live with no indication. Use the Cloudflare API or dashboard to verify deployment state after pushing.