Summary
v3.8.0 evolves the template from local validation into continuous and post-deploy validation. It adds CI for every push/PR, a deploy doctor for remote health checks, and configurable remote OpenClaw paths for non-root or custom-path deployments.
Added
- GitHub Actions workflow:
.github/workflows/validate.ymlrunsnpm teston pushes and pull requests tomain. deploy/doctor.sh: SSH-based post-deploy health checks for Node/npm, OpenClaw CLI,openclaw.jsonpermissions, workspace context files, local skills, Gateway service, Gateway/health, and Chroma memory.- Remote path configuration in
deploy/config.sh.example:REMOTE_HOMEREMOTE_OPENCLAW_HOMEREMOTE_CONFIG_HOMEREMOTE_WORKSPACE_DIR
Fixed / Improved
deploy/generate-config.shnow writesagents.defaults.workspacefrom the configured remote workspace path instead of hardcoding/root/.openclaw/workspace.deploy/deploy.shnow uses configured remote paths for OpenClaw home, workspace uploads, systemd user service location, generated config deployment, and skill installation.deploy/ip-isolate.shnow uses configured OpenClaw and systemd user paths when injecting Gateway proxy settings.- README quick-start now shows the correct working-directory flow:
cd .. && npm test, thencd deploy && ./deploy.sh, then./doctor.sh. npm testnow verifies CI workflow presence, doctor script presence, currentb2b_tradeskill count, and non-root workspace path generation.
Verified
npm testbash deploy/doctor.sh --dry-runwith generated validation configbash deploy/deploy.sh validation-client --dry-runwith generated validation configgit diff --check
Next Evolution Ideas
- Add
deploy doctor --jsonfor machine-readable health checks in automation. - Add one validated industry pack next: landing/product KB + first-touch messages + lead-discovery queries.
- Add an issue template for new industry packs so contributors submit complete, testable packs.