portal

T

Deploy / deploy (push) Successful in 29s

Details

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

.gitea/workflows

Fix static asset 404s and build-time SITE_NAME

2026-08-04 20:46:00 +02:00

public

Initial commit: content-driven onboarding portal

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

src

Hot-reload content on a NATS trigger instead of requiring a restart

2026-08-05 07:20:40 +02:00

style

Initial commit: content-driven onboarding portal