druid520/reze-test
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

reze: Make the CI deploy step manual-only

Browse Source 
Dokploy deploys are triggered from the UI, so the pipeline no longer runs on
push to trunk. The file stays as a template: it is a no-op unless DEPLOY_URL is
available, and the trigger can be switched back to push-on-trunk.
This commit is contained in:
reze
2026-10-21 09:07:15 +00:00
parent 58f585b691
commit dfe3e94aa4
2 changed files with 25 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -3
View File
@@ -176,9 +176,10 @@ and ships a `HEALTHCHECK` that polls `http://127.0.0.1:3000/healthz` with `wget`
- Build type: Dockerfile (or "Nixpacks" — the app needs nothing but Node).
- Environment variable: `PORT=3000`.
- Exposed port: `3000`.
- CI hook: add the repository secret `DEPLOY_URL` (the Dokploy deploy webhook URL).
`.woodpecker.yml` posts to it on every push to `trunk` so Dokploy rebuilds and
redeploys the service.
- Deploys are triggered from the Dokploy UI (or a Gitea webhook configured there).
CI does not deploy automatically: `.woodpecker.yml` is a manual-only template. If you
want a push-to-deploy hook, set a `DEPLOY_URL` repository variable (the Dokploy deploy
webhook URL) and switch the pipeline trigger back to `event: push` on `trunk`.
## License