reze
dfe3e94aa4
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.
29 lines
1008 B
YAML
29 lines
1008 B
YAML
# Deploy template for reze-test.
|
|
#
|
|
# Automatic deploys are DISABLED: deployments are triggered from the Dokploy UI
|
|
# (or a Gitea webhook configured there), not from CI.
|
|
#
|
|
# This pipeline is manual-only and is a no-op unless a DEPLOY_URL value is
|
|
# available in the environment (set it as a Woodpecker repository variable, or
|
|
# declare it as a secret with `from_secret: DEPLOY_URL`).
|
|
#
|
|
# To turn this back into a push-to-deploy pipeline, change the trigger to:
|
|
#
|
|
# when:
|
|
# - event: push
|
|
# branch: trunk
|
|
#
|
|
# and make sure DEPLOY_URL is set. It needs access to the internal Dokploy
|
|
# network, hence `network_mode: dokploy-network`.
|
|
|
|
when:
|
|
- event: manual
|
|
|
|
steps:
|
|
deploy:
|
|
image: curlimages/curl:latest
|
|
network_mode: dokploy-network
|
|
commands:
|
|
- 'echo "reze-test: requesting redeploy from Dokploy..."'
|
|
- 'if [ -n "$${DEPLOY_URL}" ]; then curl -fsS -X POST "$${DEPLOY_URL}" -H "Content-Length: 0"; else echo "DEPLOY_URL is not set - deploy from the Dokploy UI instead."; fi'
|