🎁 Sync 2026-08-05 20:25:34

luci-theme-footstrap/root/etc/uci-defaults/30_luci-theme-footstrap

@@ -101,8 +101,9 @@ mkdir -p /etc/footstrap 2>/dev/null
 # response by extension, and an SVG served as application/octet-stream is one no browser will
 # paint — as a CSS mask, as a background image or at all.
 [ -d /www/luci-static/footstrap ] && ln -sf /etc/footstrap/pattern.svg /www/luci-static/footstrap/pattern.svg 2>/dev/null
-# The admin-installed webfonts (fonts/set-font.sh) are a whole DIRECTORY rather than one file: the
-# faces plus the @font-face sheet generated next to them. Same arrangement as the two images above,
+# The admin-installed webfonts (/etc/footstrap/fonts, see partials/head.ut) are a whole DIRECTORY
+# rather than one file: the faces plus an @font-face sheet beside them. Same arrangement as the two
+# images above,
 # and linking a directory has TWO traps, both of which end with `ln` exiting 0 and the link sitting
 # one level too deep, at .../fonts/fonts — where no browser looks, so the fonts silently do not
 # serve and nothing reports a thing:

luci-theme-footstrap/root/lib/upgrade/keep.d/luci-theme-footstrap

@@ -1,7 +1,7 @@
 # Preserve what the ADMIN put on this router across sysupgrade: the login/page background
 # (Appearance -> Wallpaper -> File), the wallpaper pattern (Appearance -> Wallpaper -> Pattern) and
-# the webfonts installed by fonts/set-font.sh. All three are written at runtime — an upload or a
-# script, never the package — so all three survive a package upgrade on their own; a firmware
+# the webfonts the admin put in /etc/footstrap/fonts. All three are written at runtime — an upload
+# or the admin, never the package — so all three survive a package upgrade on their own; a firmware
 # sysupgrade, however, only keeps paths listed here (or in a conffile / /etc/sysupgrade.conf).
 # NOT conffiles: they live outside root/etc/config, and tools/conffiles.mjs would reject a
 # conffiles-define entry the package does not ship.