You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: deploy to /opt/nanoclaw instead of user home directory
Eliminates cross-user permission issues by using a shared /opt path.
Removes sudo wrapper and sg docker — root operates directly.
Auto-clones repo on first deploy. Hardcodes config path.
|`/update-nanoclaw`| Bring upstream NanoClaw updates into a customized install|
32
+
|`/qodo-pr-resolver`| Fetch and fix Qodo PR review issues interactively or in batch |
33
+
|`/get-qodo-rules`| Load org- and repo-level coding rules from Qodo before code tasks |
34
34
35
35
## Deployment
36
36
37
-
Production runs on a GCP VM (`nanoclaw` in `europe-west9-a`, project `minitap-sandbox`) as a Docker container at `~/nanoclaw`.
37
+
Production runs on a GCP VM (`nanoclaw` in `europe-west9-a`, project `minitap-sandbox`) as a Docker container at `/opt/nanoclaw`.
38
38
39
39
Architecture: NanoClaw host container spawns agent containers as siblings via Docker socket mount (not Docker-in-Docker). `HOST_PROJECT_ROOT` env var maps container paths to host paths for volume mounts.
40
40
41
+
Deployments are automated via GitHub Actions on push to `main`. See `.github/workflows/deploy.yml`.
0 commit comments