1.6 KiB
SHZ Test Deployment
Authorization gate
Run a commit or deployment only if the user's current request explicitly authorizes it, names the test environment, and identifies the backend, PC frontend, or both. A request to complete a task, verify a fix, or describe deployment is not authorization to run these commands.
Before running a deployment command:
- Inspect the selected repository's
git statusand diff. - Stage and commit only the files required for the task after focused local validation succeeds.
- Do not include credentials, unrelated changes, or generated artifacts unless the user explicitly includes them in scope.
- Do not push unless the user explicitly requests a push.
Backend test deployment
Use only for an explicitly authorized shz-backend test deployment:
ssh root@47.111.103.66 sh /data/code/shz-backend/buildAndStart-test.sh
This command changes the remote test environment and can restart its backend service. After it finishes, inspect the requested test route and, on a failure, read a bounded test-log window with $inspect-shz-logs.
PC frontend deployment
Use only for an explicitly authorized shz-admin PC frontend deployment:
sh /Users/lapuda/code/shz-admin/scripts/deploy-frontend.sh
Run the command locally. After it finishes, use Chrome DevTools to reload and verify the requested PC test route.
Production
No production deployment command is configured in this skill. The production base URL is not deployment authority. Require a separate, explicit current-request authorization and the exact command before any production deployment.