-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
It would be very helpful to have a canonical production deployment example for chat-ui, covering a real-world setup beyond local development and basic Docker usage.
Current state
The docs cover:
• local development
• Docker examples
• high-level deployment notes
However, they don’t clearly explain production deployments, especially regarding:
• asset paths (e.g. manifest.json)
• build-time vs runtime environment variables
• reverse proxies
• subpath deployments (e.g. /chat, /chatui)
Suggested improvement
Add a single, opinionated “recommended production deployment” example, including:
• required environment variables
• when variables must be set (build vs runtime)
• asset base/path configuration
• a minimal reverse-proxy example (e.g. Nginx)
Even one supported reference setup would greatly reduce trial-and-error.
Without a canonical example, production users like me may spend significant time debugging configuration issues rather than using or contributing to the project.
PS.: If this is already documented somewhere, or if I am misunderstanding the intended deployment model, i’d really appreciate being pointed to the correct reference.
Thank you for your work
All the best