deploy: drop Gitea Actions deploy job, cron autodeploy is sole path
CI / quality (push) Successful in 43s
CI / e2e (push) Successful in 1m33s
CI / lighthouse (push) Failing after 25s
CI / relay (push) Successful in 34s
CI / images (push) Failing after 12s

This commit is contained in:
cesnimda
2026-07-12 15:27:20 +02:00
parent 4cd7b3d88a
commit 97f23f7a02
2 changed files with 3 additions and 18 deletions
-16
View File
@@ -1,16 +0,0 @@
name: Deploy
# Auto-deploy on push to main. Runs on the self-hosted Gitea runner (which has the
# host Docker socket) and rebuilds + restarts the stack on the same host.
# The public site ends up on host port 1337 (see deploy/docker-compose.yml).
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Build and (re)start the stack
run: docker compose -f deploy/docker-compose.yml up -d --build --remove-orphans
+3 -2
View File
@@ -65,8 +65,9 @@
(nginx static, publishes 1337) + `deploy-relay-1` (contact relay, internal). Verified: all
routes + `/no/`, case studies, CV PDFs, images, `/Linkedin` 301, `/api/contact` proxy.
- **Auto-deploy:** a 1-minute cron on the host (`deploy/autodeploy.sh`) pulls `main` and
`docker compose up -d --build` on change. `.gitea/workflows/deploy.yml` also exists for the
Gitea runner (activate once its job image has the Docker CLI + socket).
`docker compose up -d --build` on change. Sole deploy path — the Gitea Actions `deploy.yml`
job was removed (its runner's job containers have no Docker socket, and mounting one in would
give any CI job root-equivalent host access).
- Repo cloned at `/home/pi/resumesite` (remote carries the deploy token — rotate/scrub if desired).
## Owner action remaining