@lifeaitools/rdc-skills 0.26.1 → 0.26.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/commands/deploy.md +16 -0
- package/git-sha.json +1 -1
- package/package.json +1 -1
package/commands/deploy.md
CHANGED
|
@@ -155,6 +155,22 @@ _COOLIFY=$(curl -s http://127.0.0.1:52437/v/coolify-api)
|
|
|
155
155
|
curl -s -H "Authorization: Bearer $_COOLIFY" "$DEPLOY_API_BASE/api/v1/applications"
|
|
156
156
|
```
|
|
157
157
|
|
|
158
|
+
**Triggering the actual deploy is different — use the wrapper, not raw curl.**
|
|
159
|
+
`hooks/lib/guard-rules.mjs`'s `coolify-direct` rule blocks a raw curl (or any command whose
|
|
160
|
+
TEXT contains the literal URL) to `/api/v1/deploy` — the deploy-trigger endpoint — on
|
|
161
|
+
purpose, so a production deploy is never one arbitrary curl an agent can fire silently. This
|
|
162
|
+
is NOT a bug to route around with SSH or a differently-worded command
|
|
163
|
+
(`.rdc/lessons/2026-08-07-deploy-coolify-direct-blocks-own-documented-step.md`). The
|
|
164
|
+
sanctioned way to actually trigger a deploy for Mode 1's "Deploy triggered" step is:
|
|
165
|
+
|
|
166
|
+
```bash
|
|
167
|
+
python3 scripts/coolify-deployments.py deploy <application-uuid>
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
Run from the regen-root repo root. Poll `status <deployment-uuid>` (the same script) or
|
|
171
|
+
`GET /api/v1/deployments/<deployment-uuid>` (read-only, not blocked) until `status` is
|
|
172
|
+
`finished`/`failed`/`cancelled` before moving to the gate checks.
|
|
173
|
+
|
|
158
174
|
If clauth daemon is not responding:
|
|
159
175
|
```
|
|
160
176
|
BLOCKED: clauth daemon not responding. Run scripts\restart-clauth.bat, unlock at http://127.0.0.1:52437
|
package/git-sha.json
CHANGED