Updates to work around cloudflare tunnel
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/push/build Pipeline was successful
ci/woodpecker/push/deploy Pipeline was successful

This commit is contained in:
2026-07-14 00:02:16 -03:00
parent 276551edb3
commit e59e694363
6 changed files with 17 additions and 12 deletions
+10 -8
View File
@@ -8,7 +8,7 @@ Pre-rendered Svelte gallery site served by Nginx. Build outputs to `build/`; ima
- **CSS:** PostCSS (nesting + level 2), component-scoped styles; critical CSS inlined at build time with Beasties.
- **Runtime:** `nginx:alpine` (see `Dockerfile`) serves the contents of `build/`.
- **Registry:** Gitea at `git.mifi.dev` → image `git.mifi.dev/mifi-holdings/armandine`.
- **Deploy:** Portainer on Linode; stack uses this image (no volume for site content).
- **Deploy:** Dockhand git stack from `deploy/docker-compose.yml`; stack uses this image (no volume for site content).
## Local development
@@ -71,7 +71,7 @@ Ports:
```bash
pnpm docker:push
```
Then on the server, redeploy the stack (e.g. Portainer “Pull and redeploy or your webhook).
Then on the server, redeploy the stack (e.g. Dockhand sync/redeploy or your webhook).
## Woodpecker CI/CD
@@ -81,7 +81,7 @@ Three pipelines (see `.woodpecker/`):
|----------|------|------|
| **ci** | Every push to `main`, every PR | Lint (ESLint + Stylelint), Prettier check, Svelte/TypeScript check |
| **build**| Push/tag/manual on `main` only (after ci) | Build site to `build/`, build Docker image, push to `git.mifi.dev/mifi-holdings/armandine` |
| **deploy** | After build | Trigger Portainer stack redeploy via webhook |
| **deploy** | After build | Trigger Dockhand stack redeploy via webhook |
Order: **ci** → **build** → **deploy**.
@@ -91,14 +91,15 @@ Configure in the repos Woodpecker secrets:
- `gitea_registry_username` Gitea user for registry login
- `gitea_package_token` Gitea token with package read/write
- `portainer_webhook_url` Portainer stack webhook URL for redeploy
- `dockhand_webhook_url` Dockhand stack webhook URL for redeploy
- Mattermost/Discord webhook secrets (see `.woodpecker/*.yaml` for notifications)
## Server / Portainer
## Server / Dockhand
- Stack is defined by `docker-compose.yml` in this repo.
- Runtime stack lives in `deploy/docker-compose.yml` only (thin git-stack context so Dockhand/Hawser does not sync `static/` media).
- In Dockhand, set compose path to `deploy/docker-compose.yml` and leave **Context directory** empty (or `deploy`) — do not set context to `.`.
- Compose uses the image from the registry (`git.mifi.dev/mifi-holdings/armandine:latest`); no volume for site content (its inside the image).
- Ensure the server can pull from `git.mifi.dev`. After a push, either let the deploy pipeline trigger the Portainer webhook or manually “Pull and redeploy the stack.
- Ensure the server can pull from `git.mifi.dev`. After a push, either let the deploy pipeline trigger the Dockhand webhook or manually sync/redeploy the stack.
## Project layout
@@ -127,7 +128,8 @@ Configure in the repos Woodpecker secrets:
│ └── critical-css.js # Beasties post-step on build/
├── build/ # Output of pnpm build (Vite + Beasties)
├── Dockerfile # nginx:alpine + COPY build/
├── docker-compose.yml
├── deploy/
│ └── docker-compose.yml # Thin Dockhand/Hawser runtime stack only
├── package.json # Scripts: dev, build, preview, check, lint, format
├── .devcontainer/
├── .woodpecker/