- How do I install alizharb/filament-themer-luncher in a Laravel Filament app?
- Install the package with Composer, then publish its configuration and register it with your Filament panel according to the package documentation. Confirm that your app already uses Laravel Themer ^1.4, PHP 8.3 to 8.5, and a compatible Filament version. The notes do not mention database migrations, so migration risk appears low.
- Which Laravel and PHP versions does filament-themer-luncher support?
- The package has CI coverage for Laravel 12 and 13 and supports PHP 8.3 through 8.5. Laravel 11 is intentionally excluded because of Composer security advisories. It also requires Laravel Themer ^1.4, so verify that dependency before installing.
- Is it safe to allow ZIP, Git, and remote theme installs from the Filament admin panel?
- The package includes hardening such as ZIP traversal protections and safe Git process arguments, but remote, Git, and ZIP installs still carry risk. URL host and local path allowlists are optional, so the default posture may be permissive unless you configure them. Enable allowlists and backup-before-activate in staging before using UI-driven installs in production.
- Are the URL host and local path allowlists enabled by default?
- The provided evaluation says the new allowlists for URL hosts and local paths are optional, so they may not be enabled by default. Treat them as opt-in and verify the published configuration. Enable them explicitly before testing remote, Git, or ZIP install workflows.
- How do theme backups and restore work in filament-themer-luncher?
- The package supports theme backup and restore workflows, and backup-before-activate appears to be configurable. The notes do not specify where backups are stored, how long they are retained, or whether restoration is fully available from the UI. Verify those details in the package configuration and test restoration in staging before production use.
- Does filament-themer-luncher support multi-tenant or multi-site theme assignments?
- Multi-tenant and multi-site behavior is not confirmed in the provided evaluation and remains an open question. The package is designed for Filament admin panels over Laravel Themer, but tenant-specific theme assignment is not documented in the notes. Confirm this against the package source or documentation before relying on it.
- Which Filament versions are compatible with filament-themer-luncher?
- The package requires a Filament admin panel, but the supported Filament major versions are not stated in the provided notes. You must verify compatibility against your project's Filament version. Test the plugin registration, theme switcher, widgets, and diagnostics pages in staging first.
- Can I use filament-themer-luncher without Laravel Themer?
- No. The package requires Laravel Themer ^1.4 and is additive rather than a replacement. It surfaces and hardens Laravel Themer capabilities inside Filament, including health, diagnostics, metadata, and install or activation workflows. If you do not already use Laravel Themer, this package is not a standalone theme manager.
- How do I upgrade from an earlier Luncher version?
- Review configuration changes for allowlists, backup behavior, and cache refresh fallback before upgrading. Re-run diagnostics after the upgrade and test theme health badges and install workflows in staging. No database migration is mentioned, which lowers migration risk, but Laravel Themer and Filament compatibility should still be checked.
- When should I avoid filament-themer-luncher or consider alternatives?
- Avoid it if your admin stack is not Filament, if you are on Laravel 11, or if your team does not want UI-driven theme installs. It is also a poor fit for legacy PHP or Laravel applications that cannot meet the PHP 8.3 to 8.5 and Laravel Themer ^1.4 requirements. CLI-only Laravel Themer workflows or custom Filament pages may be better for teams that want tighter control.