- scaling.md: Link each step to relevant troubleshooting sections
(DB corruption, WebSocket errors, login loops, worker crashes,
file access issues, logging, OpenTelemetry)
- multi-replica.mdx: Add scaling guide link in intro and Related Docs,
plus links to Redis and RAG troubleshooting
- performance.md: Add scaling guide link in Scaling Infrastructure section
- redis.md: Add scaling guide link in "When is Redis Required?"
- connection-error.mdx: Add links to Redis tutorial, scaling guide,
and multi-replica WebSocket troubleshooting
- Helm.md: Add scaling guide link alongside existing HA guide link
https://claude.ai/code/session_01TPoquFdHG6dZxRrZ4Jormh
ChromaDB's default local PersistentClient uses SQLite which is not fork-safe.
When uvicorn forks multiple workers, concurrent writes crash workers instantly.
Added warnings and guidance across env config, HA/scaling, performance,
troubleshooting, Docker Swarm, Helm, Redis, RAG, and enterprise architecture docs.
https://claude.ai/code/session_01TPoquFdHG6dZxRrZ4Jormh
This commit strengthens the warnings in the Redis and Nginx Proxy Manager documentation regarding the `C-S_ALLOW_ORIGIN` environment variable.
- Replaced the `:::tip` block with a more prominent `:::danger` block in both files.
- Clarified that a misconfigured `CORS_ALLOW_ORIGIN` is a common and difficult-to-debug cause of WebSocket connection failures, especially in production or reverse-proxied setups.
- Emphasized that this step is critical and should not be skipped.
Adds a tip to the Redis integration documentation to mention the necessity of `CORS_ALLOW_ORIGIN` for WebSocket connections. This is a common issue that can be difficult to debug.
