Hugo site with Woodpecker CI -> Surfer deploy pipeline

Builds the site with hugomods/hugo:dart-sass-node-git and syncs public/
to the Surfer app on the same Cloudron server (surfer put --all --delete).
README covers full setup: Gitea OAuth app, Woodpecker env.sh forge config,
agent options, and repo secrets.
This commit is contained in:
Nathan Schneider committed 2026-10-02 17:37:36 -06:00
commit 346c859eb5
8 files changed
+480

No files matched your search

+14
View File
@@ -0,0 +1,14 @@
---
title: Home
---
# It is alive!
This static site is deployed automatically:
1. You push a commit to `main` on **Gitea** (same Cloudron server).
2. **Woodpecker CI** picks up the push, builds the site with Hugo.
3. The build output is uploaded to **Surfer**, which serves it.
That's it — no credentials in the repo, no manual uploads. Push something to
`main` right now and watch the pipeline in Woodpecker.
+19
View File
@@ -0,0 +1,19 @@
---
title: About
---
This example shows a complete, self-hosted publishing pipeline on a single
Cloudron server:
| Stage | App | Example location |
| ----- | --- | ---------------- |
| Source | Gitea | `https://gitea.cloudron.example` |
| Build | Woodpecker CI | `https://woodpecker.cloudron.example` |
| Serving | Surfer | `https://surfer.cloudron.example` |
The pipeline is defined by a single checked-in file, [`.woodpecker.yml`](https://woodpecker-ci.org/docs/usage/workflow-syntax), and the only
secrets it needs are a Surfer domain and an access token. See the repository
README for full setup instructions.
Delete this page or rewrite everything — the templates in `layouts/` are
deliberately small so you can replace them with a real design.