🐛 Bugfix: Why did MarkdownService 404 on /api/sync/files in dev?

Date: 2026-03-14
Time: 14:32:22 UTC
Session: gspace1-219.3
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Why did MarkdownService 404 on /api/sync/files in dev?

Task: Fix 404 on docs content loading

🎯 Decision Made

Chosen:

Set docsApiUrl undefined so MarkdownService uses static files

Options Considered:

1. Add /docs-api proxy and point docsApiUrl to it
2. Set docsApiUrl undefined so MarkdownService uses static files
3. Run backend-docs-api locally and use it for content

💭 Reasoning

Root cause: docsApiUrl was /api. MarkdownService called /api/sync/files/... which proxied to backend-api (3000). backend-api has no /sync/files. backend-docs-api has it at /docs-api/sync/files. For default dev, content is served from filesystem. Setting environment.docsApiUrl=undefined makes MarkdownService use tryLoadFromStaticFiles. DocsApiService still needs /api for admin; provideApiConfig passes /api for that. Split: MarkdownService reads environment; DocsApiService uses DI token.

📁 Files Involved

• apps/docs-angular/src/environments/environment.ts
• apps/docs-angular/src/app/services/markdown.service.ts
• apps/docs-angular/src/app/app.config.ts

🔗 Related

• Decision ID: dev_1773498742269_t6ldgu7
• Session: 219
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation