mifi-ventures/landing
1
1
Fork 0
Code Pull Requests Actions Packages Releases Activity

Woodpecker updates
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Details

Browse Source
This commit is contained in:
Mike Fitzpatrick
2026-01-30 20:47:26 -03:00
parent 2600d27cbd
commit 46e45581fe
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
.woodpecker.yml
View File

@@ -2,10 +2,10 @@
# Deploys static site to Linode VPS via Docker # Deploys static site to Linode VPS via Docker
# Documentation: https://woodpecker-ci.org/docs # Documentation: https://woodpecker-ci.org/docs
# Trigger: Push to main branch or tag creation # Trigger: Push to main, tag creation, or manual run from Woodpecker UI
when: when:
branch: main branch: main
event: [push, tag] event: [push, tag, manual]
steps: steps:
# ============================================ # ============================================
@@ -99,3 +99,8 @@ steps:
# Portainer: Add stack from "Git repository" with this repo, compose path # Portainer: Add stack from "Git repository" with this repo, compose path
# docker-compose.yml. Enable GitOps → Webhook and "Re-pull image". # docker-compose.yml. Enable GitOps → Webhook and "Re-pull image".
# Add Gitea registry in Portainer (Settings → Registries) so the host can pull. # Add Gitea registry in Portainer (Settings → Registries) so the host can pull.
#
# If pipeline doesn't run on push: ensure the repo is activated in Woodpecker,
# Gitea has a webhook to Woodpecker for this repo, and your default branch is main.
# If Gitea and Woodpecker run on the same host, Gitea may need [webhook]
# ALLOWED_HOST_LIST=external,loopback in app.ini so webhooks can reach Woodpecker.