Compare commits

..
3 Commits
Author SHA1 Message Date
bl c20d13ec2e Lint with iris v0.5.2, matching the portal this runs
Deploy instance / deploy (push) Successful in 3s
lint-and-reload / lint (push) Successful in 1s
2026-09-28 18:25:31 +02:00
blandClaude Opus 5 e7fa3c6d3b Deploy this instance from CI
Kasse's runner can now ship a portal release here, the way the ergo
sites already do: PORTAL_RELEASE is the pin, and bumping it is the
rollout. No more ssh and a script run by hand across all three
instances at once.

The runner is not root. It may run one script, which checks the
instance against a fixed list and the tag against a release-tag shape
before it touches anything, and then health-checks the site without a
forwarded header - so a check cannot pass while the site is broken for
everything that is not Caddy, which is how v0.5.1 got out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-28 18:24:13 +02:00
bl 22fb006b77 Lint with iris v0.5.1
lint-and-reload / lint (push) Failing after 1s
2026-09-28 17:53:56 +02:00
3 changed files with 36 additions and 34 deletions

No files matched your search

+35
View File
@@ -0,0 +1,35 @@
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.5.2
INSTANCE: westra-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"
+1 -1
View File
@@ -14,7 +14,7 @@ jobs:
rm -rf checkout && git clone --depth 1 https://prosjekt.klingenbergbygg.no/westra/questions.git checkout rm -rf checkout && git clone --depth 1 https://prosjekt.klingenbergbygg.no/westra/questions.git checkout
- name: lint - name: lint
env: env:
IRIS_RELEASE: v0.3.39 IRIS_RELEASE: v0.5.2
run: | run: |
curl -sfL "https://project.uhhm.no/uhhm/iris/releases/download/$IRIS_RELEASE/iris" -o iris && chmod +x iris curl -sfL "https://project.uhhm.no/uhhm/iris/releases/download/$IRIS_RELEASE/iris" -o iris && chmod +x iris
./iris check --path checkout/questions ./iris check --path checkout/questions
-33
View File
@@ -22,36 +22,3 @@ alternatives:
- from: open - from: open
to: answered to: answered
label: Marker som besvart label: Marker som besvart
- name: Inviter en kollega
description: >
Gi en kollega tilgang til dette skrivebordet. Vi oppretter
kontoen og sender deg en engangslenke der de selv velger passord
eller passnøkkel — send den videre til dem.
action: /henvendelser
consequence: [Inviter]
invite:
group: westra
encouragements:
- Lenken virker i ett døgn.
features:
- name: Hvem
description: Navn slik det skal vises, og e-posten kontoen knyttes til.
requirements:
- name: name
label: Navn
- name: email
label: E-post
type: email
- name: Inviterte
description: >
Hver invitasjon med lenken som ble laget. Marker som ferdig
når kollegaen er inne.
resource:
source:
kind: kv
bucket: portal_invites
requires_group: westra
transitions:
- to: done
label: Er inne