-
26.4-alpha
Pre-releaseSome checks failedBuild ISO / build-iso (push) Successful in 26m22sDeploy site / deploy (push) Successful in 3sCI / lint (push) Successful in 26sCI / test (push) Successful in 1m37sCI / markdown-links (push) Successful in 33sRelease / release (push) Successful in 6sCI / validate-json (push) Failing after 14m0sreleased this
2026-04-18 14:31:04 +02:00 | 27 commits to main since this releaseAdded
- Local HTTPS via Caddy
tls internalon port 443. Caddy generates a per-box local root CA on first start; the Caddyfile now serves both:80and:443from the same routes. HTTP stays on by default — no regression for users who haven't trusted the CA yet. New "Local HTTPS" section in/settingsshows the CA's SHA-256 fingerprint, offers a one-click download ofrootCA.crt, links to the per-OS install guide at/https-install/, and exposes an opt-in "force HTTPS" toggle that only unhides itself once the current browser has already trusted the cert (so enabling it can't lock the user out of the settings page). Backend:GET /api/furtka/https/statusandPOST /api/furtka/https/forceinfurtka.https. The force toggle drops a Caddy import snippet into/etc/caddy/furtka.d/redirect.caddyfileand reloads Caddy; reload failure automatically rolls the snippet state back so a bad config can't wedge the next service start. - Impressum + Datenschutzerklärung on furtka.org (both DE and EN) covering §5 DDG and Art. 13 GDPR. Linked from the site footer on every page; bilingual with DE as the legally binding version.
- Auto-deploy of furtka.org on push-to-main. New
.forgejo/workflows/deploy-site.ymlruns on the self-hosted runner (which is forge-runner-01 — the webserver host), so the deploy is just a local rsync +hugo --minifyinto/var/www/furtka.org/. No SSH, no secrets. Manualwebsite/deploy.shremains for out-of-band deploys. - Post-build smoke VM on Proxmox test host 192.168.178.165. Every
build-isorun boots the freshly built ISO in a throwaway VM on pollux (8 GiB RAM / 2 vCPU — the 4 GB default OOM-ed the host during mkinitcpio), then curls:5000to confirm the webinstaller is alive. VMs in VMID range 9000–9099 tagged with the commit SHA; last 5 kept for post-mortem debugging. Optionalworkflow_dispatch"Smoke latest ISO" re-tests the cached ISO in ~2 min without rebuilding. Step-levelcontinue-on-errormeans a VM-side flake doesn't mark the ISO build red.
Fixed
- Settings page "Installed" field now refreshes after a self-update. The
/api/furtka/update/checkresponse already carriescurrent— the settings JS now drivesupd-currentfrom it the same way it drivesupd-latest, so clicking "Check for updates" after a successful update reflects the new installed version without a force-reload. - Auto-reload on update completion is now reliable. Clicking "Update now" arms a 45 s fallback
setTimeout(location.reload)in addition to the existing/update-state.jsonpolling loop. If the mid-apply API restart drops the poll connection beforestage: doneis ever observed (as seen on the 2026-04-16 VM test), the fallback still brings the page up on the new version. The fallback is cleared ondone(5 s reload wins) orrolled_back(user needs the error visible). - Version string in the webinstaller footer was pinned at
26.0-alphaand didn't track releases. Bumped to26.4-alphafor this release; follow-up will make it render frompyproject.tomldynamically.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Local HTTPS via Caddy