Document how to configure frontend-backend communication for remote access.
The Vite dev server proxy (/api -> localhost:5001) only works in local development.
When deploying on a VPS or accessing from a different machine, users must set
VITE_API_BASE_URL to the server's actual IP/URL.
Changes:
- Add VITE_API_BASE_URL to .env.example with usage instructions
- Add remote deployment note to README.md (English)
- Add remote deployment note to README-ZH.md (Chinese)
- Deleted docker-compose.yml, backend Dockerfile, frontend Dockerfile, and nginx configuration to streamline project setup.
- Updated .env.example to reorganize LLM and ZEP API configurations for clarity and ease of use.
- Enhanced README.md to reflect changes in project structure and provide clearer setup instructions.
- Updated .env.example to reflect new LLM configuration with Aliyun's API.
- Enhanced .gitignore to include additional files and directories for better exclusion of sensitive and build artifacts.
- Added docker-compose.yml for streamlined deployment of backend and frontend services.
- Introduced Dockerfiles for both backend and frontend to facilitate containerized builds.
- Created README.md to provide comprehensive project documentation and setup instructions.
- Established nginx configuration for frontend to support API proxying and static file serving.
- Updated .env.example to include new keys for dual LLM configuration, allowing for both general and boost settings.
- Modified create_model function to support an optional use_boost parameter, enabling the selection of either general or boost LLM configurations based on availability.
- Improved logging to indicate which LLM configuration is being used during model creation, enhancing clarity for users.
MiroFish Contributor
666ghj