4 Commits

Include renames

Author	SHA1	Message	Date
Bendik Aagaard Lynghaug	44c8c9d410	Add prosekit rich-text field, Gitea repo embeds, automation KV read endpoint; fix apex/www session-cookie mismatch on /auth/callback ... - type: prosekit requirement kind, backed by public/prosekit-editor.js (ProseMirror via prosekit, loaded from esm.sh, no bundler) - mirrors its HTML into a paired hidden input so it reuses the existing RwSignal/on:input wiring. - Pasting a project.uhhm.no/<owner>/<repo> URL in the editor embeds a repo card, resolved server-side via a new /gitea-repo handler (content::gitea_repo_handler) so the browser never needs Gitea API CORS. - New /automation/kv/{bucket} handler, bearer-token gated (AUTOMATION_READ_TOKEN), for backing automations (n8n) to read a NATS KV bucket without a browser session. - Fix: a login started on one of apex/www set its session cookie there, but Kanidm's redirect_uri is fixed to PUBLIC_URL - landing the callback on a different, empty session ("no login in progress"). Caddy now redirects www -> apex so every visit stays on one canonical host.	2026-08-05 13:45:56 +02:00
Bendik Aagaard Lynghaug	18025bf870	Hot-reload content on a NATS trigger instead of requiring a restart ... questions is now Arc<ArcSwap<HashMap<...>>> - readers do a lock-free atomic load (state.questions.load().get(&id).cloned()), never blocking on or blocked by a reload. content::watch_for_reload subscribes to portal.content.reload (published by the questions repo's own CI after it lints a push - see that repo's lint-and-reload.yml) and swaps in a freshly re-fetched HashMap on each message. A fetch/parse failure logs and keeps serving the last-good content rather than clearing it.	2026-08-05 07:20:40 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5	286fdbf67f	Load content from Gitea directly, drop the local clone; add deploy workflow ... 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