Weave Code
Photonic Filament Laravel Package
digitonic/photonic-filament
A Filament plugin for Digitonic Photonic, adding admin resources and UI for managing photos, albums, and media assets. Browse, upload, edit, and organise image content directly in Filament, making Photonic-powered galleries and media libraries easy to maintain in Laravel.
A plugin for FilamentPHP which interacts with the Photonic API to handle your media items
Frequently asked questions about Photonic Filament
- What is digitonic/photonic-filament used for?
- It is a FilamentPHP plugin that adds admin resources and UI for managing Photonic media such as photos, albums, and media assets. It lets developers browse, upload, edit, and organise image content directly inside a Filament admin panel in a Laravel application. It fits Laravel apps that already use Filament and have committed to Photonic as a media dependency. It is not intended for API-only services or non-Filament UIs.
- How do I install digitonic/photonic-filament in a Laravel app?
- Install it with Composer, confirm service provider and asset discovery, publish any config or assets, then register the plugin in your Filament panel provider. Check the package composer.json first because version 3.0.0 is framed as a Laravel 13 upgrade and may constrain PHP, Laravel, Filament, and Livewire versions. Run migrations and smoke-test media upload, selection, and deletion in staging before production.
- Which Laravel versions does photonic-filament 3.0 support?
- The 3.0.0 release is described as a Laravel 13 upgrade, so it should be treated as targeting Laravel 13 unless its Composer constraints say otherwise. The release note does not clearly state whether Laravel 12 remains supported, so verify laravel/framework constraints directly. For Laravel 11 or 12 applications, the safer option is to pin digitonic/photonic-filament to 2.1.0 until an upgrade is validated.
- Is photonic-filament compatible with Filament v3 or Filament v4?
- The provided release information does not explicitly name the supported Filament major version for 3.0.0. You should inspect the package composer.json for filament/filament and Livewire constraints before upgrading. Do not assume compatibility based only on the Laravel 13 note. A short spike branch is the quickest way to confirm the plugin registers and the media resources render correctly.
- How do I upgrade photonic-filament from 2.1.0 to 3.0.0?
- First upgrade the host application to Laravel 13 and the Filament version required by the plugin, then require digitonic/photonic-filament:^3.0 and verify package discovery. Publish config and diff it against your existing 2.x configuration, then run migrations in staging and compare schema changes. Test uploads, album management, deletion, permissions, and queue behaviour, and keep a 2.1.0 rollback branch until the rollout is stable.
- Does photonic-filament require a Photonic account or API credentials?
- Yes, the plugin interacts with the Photonic API to manage media items, so your application must have a working Photonic setup and the required API credentials or environment variables. Check the published config for the API endpoint, key, and any storage or processing options. The available notes do not clarify whether Photonic is SaaS, self-hosted, or both, so confirm that with the vendor. Without an active Photonic dependency, the plugin has little value.
- How should I test photonic-filament before using it in production?
- Create a time-boxed spike branch, upgrade Laravel and Filament to the required versions, install the plugin, and confirm the Filament resources appear. Publish config and migrations, run them against staging data, and exercise media upload, selection, editing, deletion, permissions, and queue behaviour. If Photonic offers a sandbox or non-production environment, test API interactions there first. Roll out behind a feature flag with a preserved 2.1.0 rollback path.
- What are the main production risks of adopting photonic-filament 3.0.0?
- The main risk is a major version bump described only as a Laravel 13 upgrade, which may hide breaking changes to config, migrations, assets, or API contracts. Filament, Livewire, and PHP compatibility are not fully documented in the provided notes, and the package appears to be small-vendor maintained. Pin exact versions in production and avoid floating constraints until a patch history exists. Budget time for dependency reviews and keep rollback instructions ready.
- What alternatives exist to photonic-filament for media management in Filament?
- Alternatives include Filament plugins built on Spatie Media Library, custom Filament resources over your own DAM or storage layer, or direct integration with the Photonic API without this plugin. The right choice depends on whether Photonic is already your media backend and whether you need its specific DAM features. If you are not committed to Photonic, a more general Filament media library plugin may reduce coupling.
- How is photonic-filament maintained and supported?
- Support is likely handled through GitHub issues without an SLA, which is typical for small-vendor Laravel packages. Check repository activity, release frequency, open issues, and any CI matrix before committing. Because maintenance windows may track Laravel and Filament upgrades, pin versions and schedule periodic dependency reviews. For business-critical media administration, confirm ownership and response expectations with the vendor.
Weaver
How can I help you explore Laravel packages today?