Fix local sub2api startup and API proxy#2952
Conversation
Problem: Codex/ccswitch could hit the Vite frontend on port 9005 for /responses, which returned a frontend 404 instead of reaching the backend on 9004. Local startup also required several manual steps, and copied config/runtime data risked being committed.\n\nFix: add local start/stop/status/log targets and scripts for the 9004 backend plus 9005 frontend, force Vite to use the TS config, proxy gateway routes such as /responses through Vite, move pnpm 11 settings into workspace config, and ignore local config/runtime data.
|
Thank you for your contribution! Before we can merge this PR, we need you all to sign our Contributor License Agreement (CLA). To sign, please reply with the following comment:
You only need to sign once — it will be valid for all your future contributions to this project. I have read the CLA Document and I hereby sign the CLA 0 out of 2 committers have signed the CLA. |
- Add timezone configuration issue (Asia/Shanghai not supported on Windows) - Add TOTP encryption key setup - Add upstream account configuration guide - Add CORS configuration reference - Add quick startup commands and log viewing tips Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 participant
Problem: Codex/ccswitch could hit the Vite frontend on port 9005 for /responses, which returned a frontend 404 instead of reaching the backend on 9004. Local startup also required several manual steps, and copied config/runtime data risked being committed.\n\nFix: add local start/stop/status/log targets and scripts for the 9004 backend plus 9005 frontend, force Vite to use the TS config, proxy gateway routes such as /responses through Vite, move pnpm 11 settings into workspace config, and ignore local config/runtime data.