Files
questions/.gitea/workflows/deploy.yml
T
blandClaude Fable 5.1 b4b91b5ea0
claude-issue-bot.yml (push) Invalid workflow file
Deploy instance / deploy (push) Successful in 4s
lint-and-reload / lint (push) Successful in 2s
Portal 0.13.0: linten og utrullingen peker på den
Samme binær og samme pakke som før; bare versjonen flyttes. Utgivelsen
tar med betalingsflyten, `revokes:` på en tilstand, en lint som leser
feltnavnene slik portalen selv gjør, økter som varer, og portal-repoet
som et arbeidsområde.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L5fbDkR5YogvJGebPtogQT
2026-11-05 10:13:48 +01:00

36 lines
1.2 KiB
YAML

name: Deploy instance
# This content repo owns its portal instance: which portal version runs
# on kasse. uhhm/portal only publishes versioned release artifacts;
# PORTAL_RELEASE below pins the one this site runs, so every rollout is
# a commit - auditable, and revertable by reverting it.
#
# Content-only changes never come through here: lint-and-reload
# hot-swaps those into the running instance over NATS.
#
# Runs on the host runner, because a deploy has to touch this host's
# filesystem and its units. It is allowed exactly one root action:
# /usr/local/bin/deploy-portal-instance, which checks the instance
# against a fixed list and the tag against a release-tag shape before
# it touches anything, and health-checks the site afterwards without a
# forwarded header - a check that sends the header Caddy would send
# cannot tell you the site is broken for everything that is not Caddy.
on:
workflow_dispatch:
push:
branches: [main]
paths:
- .gitea/workflows/deploy.yml
env:
PORTAL_RELEASE: v0.13.0
INSTANCE: klingenberg-portal
jobs:
deploy:
runs-on: fish
steps:
- name: Ship the pinned release and restart
run: sudo /usr/local/bin/deploy-portal-instance "$INSTANCE" "$PORTAL_RELEASE"