mirror of
https://github.com/ChuckBuilds/LEDMatrix.git
synced 2026-10-04 22:35:08 +00:00
* docs: add ARCHITECTURE and PERMISSIONS guides ARCHITECTURE.md maps the processes, the state the display and web services share through the cache, the display loop, the plugin system, the web UI and the update path, with links into the code and a where-to-start table. PERMISSIONS.md lists who owns what after install, both sudoers files (and why iptables is not granted), the polkit rule, and which scripts/fix_perms script to run as which user. Both are linked from the docs index, along with the MQTT bridge README and src/common/README.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: correct stale setup, service and troubleshooting claims - README: quick actions run systemctl on ledmatrix.service (run.py), not display_controller.py; use_short_date_format has no effect; the installer uses system pip with --break-system-packages, not a venv. - CONFIG_DEBUGGING: LEDMATRIX_DEBUG must be "true"; logs are in journald. - GETTING_STARTED, WEB_INTERFACE_GUIDE, TROUBLESHOOTING: enabling a plugin, plugin settings, brightness and Vegas settings apply without a restart; matrix hardware settings still need one. - TROUBLESHOOTING: install dependencies with sudo so the root service sees them; point permission problems at PERMISSIONS.md instead of a project-wide chown. - ADVANCED_FEATURES: real BackgroundDataService stats keys; Vegas hooks return VegasDisplayMode and None falls back to capture; cache files are 0660; fix_web_permissions.sh runs as the web user and does not touch sudoers. - STARLARK_APPS_GUIDE: only the linux-arm64 pixlet binary is downloaded. - HOW_TO_RUN_TESTS: test class examples that exist. - CLAUDE.md: PluginStoreManager, plugin_dirs.py, monorepo installs via the Trees API with ZIP fallback, requirements.txt is optional. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: mark deprecated plugin APIs and state manifest fields once Methods @deprecated("3.7.0") (the set pinned in test_deprecation.py) were shown as current API in the quick reference, API reference, advanced guide, development guide and FONT_MANAGER. Each is now marked deprecated with its replacement. FONT_MANAGER is rewritten around the current API; the override editor is gone and override methods are deprecated. Required manifest fields were stated three different ways. The API reference now has one section: the 7 schema-required fields, the 4 the store refuses without, class_name for the loader, and the 8 to set. The other guides link to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: document every src/common module and every widget - src/common/README.md covered 7 of 17 modules. It now has a table of all of them (purpose, whether plugins import it, release to floor on), a short entry each, and logging advice that matches the code. - SPORTS_UNIFICATION listed two shared modules and called sports_helpers the first; it now lists all six. - The widgets README lists all 28 registered widgets plus the support files, and absorbs the parts that only docs/widget-guide.md had (x-options.labels, x-advanced, x-display hidden, plugin-file-manager). docs/widget-guide.md is now a pointer to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(security): fix_web_permissions.sh re-hardens the root sudo helpers The script chowns the whole project to the web user. That included scripts/fix_perms/safe_plugin_rm.sh and safe_pip_install.sh -- the two helpers /etc/sudoers.d/ledmatrix_web lets the web user run as root -- so running it turned both into a root shell for whoever can edit them. It also re-grouped config_secrets.json away from ledmatrix. After the chown it now does what first_time_install.sh's Steps 11 and 11.1 do: helpers back to root:root 755, and config_secrets.json back to the web unit's User=:ledmatrix 640. Each step is non-fatal and prints the manual command if it fails. Also fixes what the script and its docs claimed: it never configured sudoers, its closing hint pointed at ./configure_web_sudo.sh (wrong path), and the README and ADVANCED_FEATURES.md said to run it with sudo, which it refuses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(security): validate and harden every sudoers drop-in the scripts write configure_wifi_permissions.sh copied its rules into /etc/sudoers.d/ledmatrix_wifi without `visudo -c`. A malformed drop-in makes sudo refuse every command for every user, which on a headless Pi leaves no way back in. It now checks first and leaves the installed file alone when the rules do not parse, as the other two writers do. (It already used mktemp, so that part of the review did not apply.) It also grants the two literal commands wifi_manager.py runs for NetworkManager's shared-mode dnsmasq drop-in -- `cp /tmp/ledmatrix-nm-dnsmasq.conf .../dnsmasq-shared.d/ledmatrix-captive.conf` and `rm -f` of that file. The directory's mkdir was granted, the file was not. Both are pinned in test_sudo_allowlist_covers_calls.py. configure_web_sudo.sh wrote its rules to /tmp/ledmatrix_web_sudoers_$$, a predictable name in a world-writable directory; it now uses mktemp with an EXIT trap, as first_time_install.sh does. It sets mode 440 on the installed file instead of leaving the temp file's mode, and finds visudo in /usr/sbin when that is not on the user's PATH, which skipped the check silently. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(install): escape the project path in the DNS-fix and MQTT unit renderers install_dns_fix.sh and install_mqtt_bridge.sh substituted __PROJECT_ROOT_DIR__ with the raw path, while the other three renderers go through sed_escape_replacement from lib_systemd_render.sh. A checkout under a path containing `&`, `\` or `|` rendered a corrupted unit from these two only. Both now source the helper and use it, and a test checks that every placeholder substitution in scripts/install uses an escaped value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(install): stop the installer scripts reporting things that are not true - first_time_install.sh printed "Password: ledmatrix123" for the setup access point. wifi_manager creates it as an open network ("No password" on the panel), so it now says so. - Step 10.1 printed "✓ WiFi management permissions configured" straight after its own failure message; install_wifi_monitor.sh printed "✓ Package installation completed" after a failed apt install. The tick now only follows success. - Step 7 printed "Web dependencies already installed ... in Step 5" in the one branch that runs because Step 5 did not install them, then created .web_deps_installed on that basis. It now warns and leaves the marker off so the next run retries, as the comment below it intends. - check_system_compatibility.sh called Debian 12 Bookworm "full compatibility confirmed" while first_time_install.sh refuses anything but Debian 13. Bookworm, older Debian and non-Debian systems are now errors. Its counters used ((X++)), which under `set -e` exits the script at the first warning or error (the expression is 0), so the check never reached its summary on any system with one. - configure_web_sudo.sh and configure_wifi_permissions.sh finished by testing `sudo -n test -f ...` and `sudo -n nmcli device status`, neither of which is granted, so they always reported a failure. They now ask `sudo -n -l` about commands the new rules do grant, which checks the rule without running anything. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(install): print the completion summary before rebooting With -y -- and so for every one-shot `curl | bash` install, which always passes -y -- first_time_install.sh ran `reboot` about 180 lines before its "Installation Complete / Web UI Access" summary. reboot returns at once, so the summary printed while the Pi was going down and the SSH session usually dropped before the web UI address could be read. The reboot block moves, unchanged, to the very end of the script. The interactive prompt now also follows the summary. Because the summary now runs before the -y reboot, its one command that could fail under `set -Eeuo pipefail` (the SSID lookup, when nmcli reports a connected device but no active network line) gets `|| true`; a missing SSID was already handled as "SSID unknown". one-shot-install.sh prints its "Next steps" after the installer returns, by which time the reboot is under way, so it now says so, and README's Quick Install mentions the automatic reboot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(scripts): correct wrong comments and messages, drop dead code No behaviour change except the output text noted below. - 2775 is setgid, not the sticky bit (first_time_install.sh Step 3.1, fix_plugin_permissions.sh), and root needs no "PWM hardware access" to plugin files. - The 777 comments in first_time_install.sh Step 3's fallback and fix_assets_permissions.sh said root needs it to write. Root ignores mode bits; the comments now say what 777 actually opens. The 777 itself is unchanged. - apt_remove ends in `|| true`, so Step 12's "Some packages could not be removed" branch could never run; it is gone and the helper stays non-fatal. - detect_web_service_user's comment named Step 8 for the web unit (install_service.sh installs it in Step 7.5) and now says which branch actually runs. - Step 5 described an "already installed" check that does not exist; the ACTUAL_USER comment described the re-exec backwards. - on_error printed a literal "\n" before "Common fixes:". - Dead code: one-shot-install.sh's uncalled fix_tmp_permissions, LEDMATRIX_ELEVATED=1 (never read) on the sudo re-exec, and configure_web_sudo.sh's unused PYTHON_PATH, which also made a missing python3 fatal for rules that never mention it. - start_display.sh / stop_display.sh said "for user: <you>"; the service runs as root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(fix_perms): fix_cache_permissions.sh uses setup_cache.sh's model There were two models for /var/cache/ledmatrix. setup_cache.sh (the installer's Step 2) and install_web_service.sh share it through the ledmatrix group: root:ledmatrix, 2775, files 660, which is also what DiskCache relies on to give files the directory's group. fix_cache_permissions.sh instead made it 777 and re-grouped it to the invoking user's group, undoing that. It now runs setup_cache.sh for /var/cache/ledmatrix and keeps its own handling of ~/.ledmatrix_cache. Dropped: /var/cache/ledmatrix/ placeholder_logos (nothing reads it) and the checks against the `daemon` user (no service runs as daemon). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ci: pin actions/checkout in the Claude workflows, drop template comments claude.yml and claude-code-review.yml used actions/checkout@v4 while test.yml and release-version-check.yml pin the v4.2.2 commit SHA; they now pin the same SHA. The commented-out starter-template settings (prompt, claude_args, paths, author filter) are removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(scripts): index every script and list removal candidates New scripts/README.md gives one line per top-level script and scripts directory, marked keep, dev-only or diagnostic, and lists the eight scripts nothing in the repo refers to as candidates for removal (kept for now). The install, utils and dev READMEs now list the files they were missing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test: tighten two checks that mutation testing showed were too loose - The wifi sudoers check matched `visudo -c -f "$TEMP_SUDOERS"` in the error report too, so replacing the check with `if false` still passed. It now requires the command as the condition. - The summary test never had the setup access point up, so reinstating the bogus "Password: ledmatrix123" line went unnoticed. A case with hostapd active now checks the AP is described as open. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(permissions): describe the repaired fix_perms scripts and new WiFi grants Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(changelog): docs-scripts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
223 lines
8.4 KiB
Markdown
223 lines
8.4 KiB
Markdown
# FontManager Usage Guide
|
|
|
|
> **Picking a size automatically:** if you want the *largest font that fits
|
|
> a given area* rather than a fixed size, use the adaptive layout system's
|
|
> font ladders, which resolve through this FontManager. `BasePlugin`
|
|
> subclasses get this as `self.layout.fit_text(...)`; other code can build
|
|
> a `LayoutContext(width, height, font_manager)` directly — see
|
|
> [ADAPTIVE_LAYOUT.md](ADAPTIVE_LAYOUT.md).
|
|
|
|
## Overview
|
|
|
|
[`src/font_manager.py`](../src/font_manager.py) loads and caches the TTF and
|
|
BDF fonts in `assets/fonts/`, registers fonts that plugins ship, and records
|
|
which plugin uses which font so the web UI can show it.
|
|
|
|
Several methods are deprecated and will be removed in LEDMatrix 3.7.0; they
|
|
log a warning on first call. They are listed in
|
|
[Deprecated methods](#deprecated-methods) below, and the full set is pinned in
|
|
[`test/test_deprecation.py`](../test/test_deprecation.py).
|
|
|
|
## Getting the FontManager
|
|
|
|
There is one shared FontManager per display process. The display controller
|
|
creates it and hands it to the `PluginManager`, so a plugin reaches it
|
|
through its `plugin_manager`:
|
|
|
|
```python
|
|
class MyPlugin(BasePlugin):
|
|
def __init__(self, plugin_id, config, display_manager, cache_manager, plugin_manager):
|
|
super().__init__(plugin_id, config, display_manager, cache_manager, plugin_manager)
|
|
self.font_manager = self._get_font_manager()
|
|
```
|
|
|
|
`BasePlugin._get_font_manager()` returns `plugin_manager.font_manager`, or a
|
|
standalone FontManager when none is available (test harnesses, mocks).
|
|
`DisplayManager` has **no** `font_manager` attribute —
|
|
`display_manager.font_manager` raises `AttributeError`.
|
|
|
|
## Resolving a font
|
|
|
|
```python
|
|
element_key = f"{self.plugin_id}.title"
|
|
|
|
# Register the choice so the web UI's Fonts tab can list it.
|
|
self.font_manager.register_manager_font(
|
|
manager_id=self.plugin_id,
|
|
element_key=element_key,
|
|
family="press_start",
|
|
size_px=10,
|
|
color=(255, 255, 255),
|
|
)
|
|
|
|
font = self.font_manager.resolve_font(
|
|
element_key=element_key,
|
|
family="press_start",
|
|
size_px=10,
|
|
)
|
|
self.display_manager.draw_text("Hello", x=10, y=10, font=font)
|
|
```
|
|
|
|
`resolve_font()` applies any entry for `element_key` in
|
|
`config/font_overrides.json`, maps a plugin-local family to its namespaced
|
|
name when `plugin_id` is passed, and then calls `get_font(family, size_px)`.
|
|
On error it returns a fallback font rather than raising.
|
|
|
|
`get_font(family, size_px)` looks the family up in `font_catalog` and loads
|
|
it (cached per family and size).
|
|
|
|
## Font families
|
|
|
|
At start-up the FontManager scans `assets/fonts/` for `.ttf` and `.bdf`
|
|
files. Each becomes a family named after the file, lower-cased and without
|
|
the extension (`PressStart2P-Regular.ttf` → `pressstart2p-regular`). Four
|
|
aliases are added on top:
|
|
|
|
| Alias | File |
|
|
|---|---|
|
|
| `press_start` | `assets/fonts/PressStart2P-Regular.ttf` |
|
|
| `four_by_six` | `assets/fonts/4x6-font.ttf` |
|
|
| `five_by_seven` | `assets/fonts/5x7.bdf` |
|
|
| `tom_thumb` | `assets/fonts/tom-thumb.bdf` |
|
|
|
|
Read the catalog directly: `font_manager.font_catalog` is a dict of family
|
|
name to file path. Files added later are picked up on the next start of the
|
|
display service.
|
|
|
|
## Plugin fonts
|
|
|
|
Plugins that ship their own fonts declare them in a `"fonts"` block in
|
|
`manifest.json`. The plugin manager calls
|
|
`FontManager.register_plugin_fonts()` during plugin load. `plugin://…`
|
|
sources are resolved relative to the plugin's install directory.
|
|
|
|
```json
|
|
{
|
|
"id": "my-plugin",
|
|
"name": "My Plugin",
|
|
"fonts": {
|
|
"fonts": [
|
|
{
|
|
"family": "custom_font",
|
|
"source": "plugin://fonts/custom.ttf",
|
|
"metadata": {"description": "Custom plugin font", "license": "MIT"}
|
|
},
|
|
{
|
|
"family": "web_font",
|
|
"source": "https://example.com/fonts/font.ttf",
|
|
"metadata": {"checksum": "sha256:abc123..."}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
```
|
|
|
|
Registered families are namespaced as `<plugin_id>::<family>`. Pass
|
|
`plugin_id` to `resolve_font()` to use the short name:
|
|
|
|
```python
|
|
font = self.font_manager.resolve_font(
|
|
element_key=f"{self.plugin_id}.text",
|
|
family="custom_font", # resolved as "my-plugin::custom_font"
|
|
size_px=10,
|
|
plugin_id=self.plugin_id,
|
|
)
|
|
```
|
|
|
|
## Overrides
|
|
|
|
`resolve_font()` still honours `config/font_overrides.json` (a map of
|
|
element key to `family` and/or `size_px`), which is read once at start-up.
|
|
The methods that edit it — `set_override()`, `remove_override()`,
|
|
`get_overrides()` — are deprecated, and there is no web UI or REST endpoint
|
|
for overrides (the override editor and `/api/v3/fonts/overrides` were
|
|
removed). To let users choose a font, add a field to your plugin's config
|
|
schema.
|
|
|
|
## Font usage in the web UI
|
|
|
|
The web UI's **Fonts** tab lists, uploads, previews and deletes the font
|
|
files in `assets/fonts/`. The web interface runs in its own process and has
|
|
no FontManager, so the display service publishes which plugin uses which
|
|
font ([`src/font_usage.py`](../src/font_usage.py)), and the tab's **Used by**
|
|
column reads it:
|
|
|
|
- **Source**: `register_manager_font()` registrations of the loaded
|
|
plugins. `get_font()` and `resolve_font()` do not know the calling plugin
|
|
and are not counted, and neither is a plugin that opens a font file
|
|
directly with PIL — register the fonts your plugin draws with if you want
|
|
them listed.
|
|
- **Names**: a family, alias or path is resolved through `font_catalog` to
|
|
the file it loads and reported under that file's name without extension
|
|
(`PressStart2P-Regular`, `4x6-font`, `5x7`, `tom-thumb`), which is how the
|
|
Fonts tab keys its rows. Fonts outside `assets/fonts/` (a plugin's own
|
|
`plugin_id::family` fonts) and families that resolve to nothing are left
|
|
out.
|
|
- **When**: a daemon thread started once plugins have loaded checks every
|
|
10 seconds and writes the `font_usage_snapshot` cache key only when the
|
|
usage changed (and once a day, so the cache's cleanup never expires it).
|
|
Unloading a plugin drops its registrations (`forget_manager_fonts`).
|
|
- **Unknown**: until the display service has published, the column reads
|
|
"unknown" and `GET /api/v3/fonts/catalog` returns `used_by: null`.
|
|
- The tab warns before deleting a font that a loaded plugin registered.
|
|
|
|
## Text measurement
|
|
|
|
```python
|
|
width, height, baseline = font_manager.measure_text("Hello", font)
|
|
font_height = font_manager.get_font_height(font)
|
|
```
|
|
|
|
## Tips
|
|
|
|
- BDF fonts usually look better than TTF at small sizes on LED panels.
|
|
- Use `{plugin_id}.{element}` element keys.
|
|
- Register the fonts you draw with, so the Fonts tab can warn before one is
|
|
deleted.
|
|
- Replace direct `ImageFont.truetype("assets/fonts/...", 8)` calls with
|
|
`resolve_font()`: it caches, resolves paths against the install directory,
|
|
and handles BDF files.
|
|
|
|
## Troubleshooting
|
|
|
|
**Font not found**
|
|
- Check the file exists in `assets/fonts/`.
|
|
- The family name is the filename without extension, lower-cased.
|
|
- Check the display service log for font discovery errors.
|
|
|
|
**Plugin fonts not loading**
|
|
- Check the manifest's `"fonts"` block.
|
|
- Check the log for download or registration errors, and that font URLs are
|
|
reachable.
|
|
|
|
## API reference
|
|
|
|
Current methods:
|
|
|
|
| Method | Purpose |
|
|
|---|---|
|
|
| `register_manager_font(manager_id, element_key, family, size_px, color=None)` | Record a font choice (feeds the Fonts tab) |
|
|
| `forget_manager_fonts(manager_id)` | Drop a manager's registrations (core calls it when a plugin unloads) |
|
|
| `resolve_font(element_key, family, size_px, plugin_id=None)` | Get a font, applying overrides and plugin namespacing |
|
|
| `get_font(family, size_px)` | Get a font directly |
|
|
| `get_native_bdf_size(family)` | Native pixel size of a BDF family, or `None` |
|
|
| `measure_text(text, font)` | `(width, height, baseline)` |
|
|
| `get_font_height(font)` | Line height |
|
|
| `register_plugin_fonts(plugin_id, font_manifest)` | Register a plugin's fonts (core calls it at load) |
|
|
| `clear_cache()` | Drop cached fonts and metrics |
|
|
| `font_catalog` (attribute) | Family name → file path |
|
|
|
|
### Deprecated methods
|
|
|
|
Removed in 3.7.0. Each logs a warning on first call.
|
|
|
|
| Method | Use instead |
|
|
|---|---|
|
|
| `get_available_fonts()`, `get_font_catalog()` | read `font_catalog` |
|
|
| `get_size_tokens()` | pass a pixel size |
|
|
| `get_performance_stats()` | — |
|
|
| `set_override()`, `remove_override()`, `get_overrides()` | a font field in your plugin's config schema |
|
|
| `get_manager_fonts()`, `get_detected_fonts()` | — |
|
|
| `get_plugin_fonts()`, `unregister_plugin_fonts()` | — |
|
|
| `add_font()`, `remove_font()`, `validate_font()` | the web UI's Fonts tab |
|