- How do I install cwsps154/my-gallery in a Laravel Filament application?
- Run composer require cwsps154/my-gallery, then execute php artisan my-gallery:install and register MyGalleryPlugin::make() inside your PanelProvider::panel() method. Because the install command appears to bundle migrations, resources, and a settings page, publish the my-gallery-config file first and inspect it before running the installer. Test the full sequence against a disposable database so you can see exactly which tables and assets the command creates.
- Which Filament version does my-gallery support, and what are the Laravel and PHP requirements?
- The plugin registration pattern MyGalleryPlugin::make() matches the Filament v3 plugin API, so v3 is the safest assumption. The available documentation does not publish a Filament major version constraint or PHP and Laravel version floors, and v1.0.0 has no LTS or deprecation signal. Check the composer.json require block on the repository before committing, and pin the exact version you validate.
- Is cwsps154/my-gallery a standalone gallery library or a Filament plugin?
- It is a Filament panel plugin rather than a framework-agnostic gallery library. It slots into an existing PanelProvider via MyGalleryPlugin::make() and assumes your admin surface is already Filament. If your admin panel is Nova, Backpack, or bespoke Blade, this package is a non-starter and you should meet the gallery requirement another way.
- How does authorization work in my-gallery?
- The plugin exposes four closures, canViewAny, canCreate, canEdit, and canDelete, plus a second overload that accepts permission and role strings when cwsps154/filament-users-roles-permissions is installed. The closure form is the portable option and can wrap Gate::allows() or Laravel Policies so the gallery is not welded to a third-party ACL. Confirm that checks are enforced server-side on direct route hits, not just hidden in the UI.
- What is the settings-page config key, and is cwsps154/app-settings a required dependency?
- The publishable my-gallery-config file has a single settings-page key that defaults to \CWSPS154\AppSettings\Page\AppSettings::class, an apparent class from the same author. The documentation does not state whether that package is a hard require or a suggest, nor whether settings-page can be set to null. Verify in a scratch application before adopting, since it implies a transitive dependency.
- Where does my-gallery store uploaded images, and can I configure the disk?
- Storage is not documented: there is no stated driver, disk configuration, upload validation, or image-derivative strategy. Gallery packages usually live or die on these decisions, so inspect the published config and the migrations created by my-gallery:install before committing. If thumbnails matter, confirm whether derivatives are generated at all and with GD or Imagick.
- Is cwsps154/my-gallery v1.0.0 stable enough for production?
- It is a first release with no deprecation runway, no LTS signal, and no referenced license, CI status, test coverage, or changelog. That does not make it unusable, but it means you own the review burden. Pin the exact version in composer.json, read the source, and wrap uploads and authorization in your own tests.
- How do I test a Filament gallery plugin like my-gallery in my application?
- No test coverage is referenced for the package itself, so plan your own feature tests around routes, authorization callbacks, and uploads. Use RefreshDatabase with Storage::fake() and assert that the canCreate and canEdit closures actually block unauthorized users. Also test the install command against a disposable database to confirm it is idempotent and rollback-safe.
- What does php artisan my-gallery:install actually do, and is it safe on an existing database?
- The command appears to bundle migrations, resources, and a settings page rather than delegating to a media library. The documentation does not state whether it also seeds data, publishes assets, or mutates PanelProvider, nor whether it is idempotent on a non-empty database. Run it first in a local or disposable environment, and review the migrations before applying them to production.
- What are the alternatives to cwsps154/my-gallery for image galleries in Laravel?
- spatie/laravel-medialibrary is the mature choice for media management and pairs with Filament via community plugins, while Filament's built-in FileUpload and Repeater components cover simple cases without extra dependencies. A custom Filament resource gives you full control over schema, disk, and derivative strategy. my-gallery trades that control for a fast install, since you inherit its storage and schema decisions wholesale.