wangzhendong/openclaw-control-plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update VPS control plane path

Browse Source 
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
wangzhendong
2026-05-15 10:56:42 +08:00
parent 9063dce0df
commit 42181b9965
4 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
handoff/ORCHESTRATOR.md
View File

@@ -18,21 +18,21 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel
- Standalone Gitea repository: `https://git.smartmotor.cloud/wangzhendong/openclaw-control-plane.git`.
- PC local path: `D:\openclaw-control-plane`.
- VPS target path: `/opt/openclaw-control-plane`.
- VPS target path: `/home/ubuntu/openclaw-control-plane`.
- Access mode: HTTPS.
- Default branch: `main`.
- Strict `smartmotor.cloud` website freeze is a hard requirement during filing review.
## Next Actions
1. Commit and push the control-plane scaffold to Gitea after user approval.
2. Clone or pull the repository on the VPS at `/opt/openclaw-control-plane`.
3. Run G0 requirements and acceptance review with the user.
4. Assign PC and VPS read-only baseline tasks only after sync is available on both machines.
1. Commit and push this path correction to Gitea.
2. Run G0 requirements and acceptance review with the user.
3. Assign PC and VPS read-only baseline tasks in their respective Cursor windows.
4. Require verifier review before any mutation.
## Open Questions
- Has the VPS cloned the control-plane repository at `/opt/openclaw-control-plane`?
- Has the VPS pulled the latest control-plane repository at `/home/ubuntu/openclaw-control-plane`?
- Should Gitea Issues be used immediately for task tracking, or should `AGENT_BOARD.md` remain the first source of truth for the initial run?
## Last Update

2
handoff/VPS_EXECUTOR.md
View File

@@ -24,7 +24,7 @@ Operate only on the VPS side: `/opt/service`, OpenClaw Gateway, Docker stack, Ng
- VPS public IP: `114.132.222.127`.
- OpenClaw Gateway is already deployed and coexists with the existing Docker stack.
- The VPS service workspace path is `/opt/service`.
- The VPS control-plane path is `/opt/openclaw-control-plane`.
- The VPS control-plane path is `/home/ubuntu/openclaw-control-plane`.
- Gitea control-plane repository: `https://git.smartmotor.cloud/wangzhendong/openclaw-control-plane.git`.
## Next Read-Only Task