Remote-Falcon/remote-falcon-plugin v2026.08.08.01

on GitHub

FPP 10 readiness release, driven by FPP's plugin-check scan (FalconChristmas/fpp-data#207) and the new PLUGIN_GUIDELINES.md.

Added

• 256x256 icon.png so the Plugin Manager shows the RF mark instead of initials.
• GitHub issue-template config routing bug reports to the central issue tracker.
• tier1-log-migration.sh hardware test covering the log rename migration.
• CI now tests PHP 8.4 (the FPP 10 runtime).

Changed

• Listener log renamed to plugin-remote-falcon.log (FPP's plugin-<repoName>.log convention, picked up by FPP's log viewer and Support Zip). Existing logs are migrated automatically on first start after upgrade.
• Log rotation is now left to FPP (which rotates all plugin logs itself); the plugin-owned logrotate config is removed, including the legacy copy under /etc/logrotate.d/ on upgraded installs.
• Lifecycle scripts resolve FPP's media/logs directories via ${FPPDIR}/scripts/common instead of hardcoding /home/fpp/media, and no longer use sudo (hooks run as root).
• Plugin UI is theme-aware: status text, sync dialog, and log tail follow FPP's light/dark theme via Bootstrap CSS variables; sync dialog is responsive at phone widths.
• Single Help menu entry (FPP allows one entry per menu area); the remotefalcon.com link lives inside the Help page.

Fixed

• Uninstall now requests an fppd restart so the plugin's registered commands don't linger as ghosts until the next unrelated restart.
• The listener refuses to run under a web SAPI, so it can no longer be started through FPP's plugin.php and pin an Apache worker.
• Removed the commented-out Patreon link and its CSS (FPP plugins may not reference donation services).

Validation

• CI green on PHP 7.4–8.4 (PHPUnit 133 tests / 297 assertions).
• Layer 4 hardware pass on a real FPP 9.5.3 Pi: restart storm, real-RF connectivity, 5-minute soak (zero RSS growth), log migration 8/8, root install under set -e, UI verified in dark theme and at 320px width.