portal

3 Commits 1 Branch 25 Tags

3 Commits

Author	SHA1	Message	Date
Bendik Aagaard Lynghaug	76d101b7a8	Share sccache between manual dev builds and CI Deploy / deploy (push) Failing after 4s Details SCCACHE_DIR/CARGO_TARGET_DIR now point at /var/local/sccache and /var/local/cargo-target, shared with the interactive dev shell via a new `builders` group, instead of the CI job hitting a leftover personal sccache server it had no permission to write build output for.	2026-08-04 13:27:22 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5	286fdbf67f	Load content from Gitea directly, drop the local clone; add deploy workflow Deploy / deploy (push) Failing after 16s Details load_questions_from_gitea (content.rs) fetches question YAML straight from the questions repo's public Gitea contents API at startup instead of scanning a local directory - one fewer moving part in production (no git clone to keep in sync, no separate questions-repo deploy workflow). Still just an in-memory startup load, same as before - served from RAM for every request, no per-request network call. Verified against the real repo (all 5 questions fetch correctly). CONTENT_DIR is replaced by CONTENT_REPO/CONTENT_BRANCH, defaulting to the real questions repo so local dev needs no env override. Also adds .gitea/workflows/deploy.yml: builds with cargo-leptos, ships the release under /srv/app/uhhm-portal (the generic app@.service deploy layout), writes /etc/app/uhhm-portal.env from this repo's own Actions Variables/Secrets, restarts the service, and drops this app's Caddy routing snippet into services.d/. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-31 06:10:06 +02:00
Bendik Aagaard Lynghaug	aa1a7fa572	Initial commit: content-driven onboarding portal Leptos/Axum app that renders a Question/Alternative/Feature schema loaded from a sibling content repo (portal-content). Kanidm OIDC login, content-driven authorization (Question.qualifies), a generic NATS KV-backed resource + state-transition mechanism (no bespoke "applicant" concept baked into the runtime - it's all content), a SHA-256 DAG chain tying submissions and decisions together, and the "YES - Rasterized Lines" piece (ported from the live uhhm.no site) as the landing hero.	2026-07-29 19:38:40 +02:00

Author

SHA1

Message

Date

Bendik Aagaard Lynghaug

76d101b7a8

Share sccache between manual dev builds and CI

Deploy / deploy (push) Failing after 4s

Details

SCCACHE_DIR/CARGO_TARGET_DIR now point at /var/local/sccache and
/var/local/cargo-target, shared with the interactive dev shell via a
new `builders` group, instead of the CI job hitting a leftover
personal sccache server it had no permission to write build output for.

2026-08-04 13:27:22 +02:00

Bendik Aagaard LynghaugandClaude Sonnet 5

286fdbf67f

Load content from Gitea directly, drop the local clone; add deploy workflow

Deploy / deploy (push) Failing after 16s

Details

load_questions_from_gitea (content.rs) fetches question YAML straight
from the questions repo's public Gitea contents API at startup instead
of scanning a local directory - one fewer moving part in production
(no git clone to keep in sync, no separate questions-repo deploy
workflow). Still just an in-memory startup load, same as before -
served from RAM for every request, no per-request network call.
Verified against the real repo (all 5 questions fetch correctly).

CONTENT_DIR is replaced by CONTENT_REPO/CONTENT_BRANCH, defaulting to
the real questions repo so local dev needs no env override.

Also adds .gitea/workflows/deploy.yml: builds with cargo-leptos,
ships the release under /srv/app/uhhm-portal (the generic app@.service
deploy layout), writes /etc/app/uhhm-portal.env from this repo's own
Actions Variables/Secrets, restarts the service, and drops this app's
Caddy routing snippet into services.d/.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-31 06:10:06 +02:00

Bendik Aagaard Lynghaug

aa1a7fa572

Initial commit: content-driven onboarding portal

Leptos/Axum app that renders a Question/Alternative/Feature schema
loaded from a sibling content repo (portal-content). Kanidm OIDC login,
content-driven authorization (Question.qualifies), a generic NATS
KV-backed resource + state-transition mechanism (no bespoke "applicant"
concept baked into the runtime - it's all content), a SHA-256 DAG chain
tying submissions and decisions together, and the "YES - Rasterized
Lines" piece (ported from the live uhhm.no site) as the landing hero.

2026-07-29 19:38:40 +02:00