Added a workflow to let the agent automatically deploy frontend onto the esp32.
This commit is contained in:
@@ -86,3 +86,19 @@ Once the backend supports it (Phase 2+), you can update the frontend without usi
|
||||
For a safer and more convenient update experience, you can bundle both the Firmware and Frontend into a single file.
|
||||
|
||||
See the [Universal OTA Bundle Guide](build_bundle.md) for details.
|
||||
|
||||
## 7. AI Agent Workflow
|
||||
|
||||
If you are an AI agent, you should use the automated deployment scripts to speed up your work.
|
||||
|
||||
### Deployment Prerequisites
|
||||
- Ensure `VITE_API_BASE` in `frontend/.env` is set to the target device IP.
|
||||
- Ensure `MKLITTLEFS_PATH` is correctly set if you are on Windows.
|
||||
|
||||
### Standard OTA Workflow
|
||||
Follow the [Frontend OTA Workflow](file:///w:/Classified/Calendink/Provider/.agents/workflows/frontend-ota.md) for automated building and deployment.
|
||||
|
||||
**Summary of commands (run in `frontend/`):**
|
||||
1. `npm run build:esp32` - Build production assets.
|
||||
2. `npm run ota:package` - Create LittleFS image.
|
||||
3. `npm run ota:deploy` - Upload to device via HTTP.
|
||||
|
||||
Reference in New Issue
Block a user