Use a tested native theme picker and a pinned Legacy repository #8
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/legacy-repository"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replace the unsafe custom English-locale override with the pinned native Forgejo 16.0.3 appearance template, changing only the two theme-label render sites. Keep every native settings form and preference ID. A small display template supplies Tilo/Tilo Dark and Tilo Legacy/Tilo Legacy Dark plus system options; built-in translations remain untouched.
Mount the complete mapped template directory, matching the tested preview, so removing an override cannot leave an empty file on the persistent volume. Original rounded CSS now comes from the pinned tilo/forgejo-theme-old repository, preserving its pre-redesign history and exact file bytes. Generated CSS/scripts remain byte-for-byte unchanged.
Validated startup and restart on the exact production image with an isolated SQLite database. Chromium/Firefox application, navigation, repository and control suites pass, including 82 contrast/link page audits. The new theme suite saves all six choices via native forms in both browsers, checking labels, geometry, palette and Legacy template gates. The temporary test instance and database were removed. Render checks validate every ConfigMap mount key and all eight template paths, with no locale override.