- What is Filament One used for?
- Filament One is a Laravel and Filament package for building single-record admin resources such as settings pages, profiles, and other focused admin screens. It removes the usual list, create, and delete boilerplate while keeping Filament's familiar forms and navigation. It is aimed at developers who want a streamlined, single-record resource pattern inside an existing Filament admin panel.
- How do I install jeddsaliba/filament-one?
- Install it with Composer into an existing Laravel application that already uses Filament, then follow the repository README for registering the resource or publishing any required assets. Check the package's composer.json for its Laravel, PHP, and Filament version constraints before requiring it. Release 1.5.0 is a semver-minor release with no documented public API or dependency changes.
- Which Laravel and Filament versions does Filament One support?
- The repository's composer.json is the authoritative source for supported Laravel, PHP, and Filament versions. The provided Docker environment uses PHP 8.3-FPM, but that does not by itself define the package's Composer constraints. Verify the constraints against your application's installed Laravel and Filament majors before adopting it.
- Can I use Filament One for settings and profile pages?
- Yes, that is the core use case. Filament One is designed for single-record resources where users edit one set of settings or one profile rather than managing a list of records. You keep Filament's form components and navigation while avoiding list, create, and delete pages that do not make sense for single-record data.
- What is the Docker Compose stack in Filament One 1.5.0 for?
- The Compose stack is a contributor and demo environment, not a production deployment reference. It includes PHP 8.3-FPM, Nginx, MySQL 8.0, Redis, and a queue worker so you can run the package in a realistic Laravel stack without provisioning services locally. Treat it as an evaluation harness you can spin up for a spike or vendor review and then discard.
- Do I need Redis and a queue worker to use Filament One?
- The included Compose stack runs Redis and a queue worker, which suggests the intended operating envelope expects them, but the package itself is an admin resource helper. Validate whether your application actually uses queues or Redis before assuming they are required. If your app does not use them, the demo stack is over-specified for simple evaluation.
- Is the Docker setup in Filament One production-ready?
- No. The stack lacks TLS termination, secrets management, health checks, and backup strategy, and Docker support in a library repository is routinely misread as a production reference. The images also appear unpinned by digest, so builds are not reproducible. MySQL 8.0 reaches end of life in April 2026, and PHP 8.3 moves into security-support-only territory by late 2026, so plan your own supported base images if you adapt anything from it.
- Are the Docker assets included in the Composer package?
- That depends on whether the repository excludes them via .gitattributes export-ignore. If they are not excluded, the Dockerfile and Compose files ship into vendor and add noise to installed packages. If they are excluded, the assets are available only from a git clone, which is acceptable but should be stated in the documentation.
- How does Filament One's Docker setup relate to Laravel Sail?
- The Compose stack overlaps with Laravel Sail, giving you two competing local-development paths, which is a real onboarding hazard. The README should state clearly whether Sail is supported, deprecated, or simply unmentioned alongside the new Docker assets. Until that is documented, pick one path for your team and avoid mixing the two.
- Can Filament One handle normal CRUD resources with lists, create, and delete pages?
- Filament One is specifically built for single-record resources and intentionally removes list, create, and delete boilerplate. For multi-record CRUD screens, use standard Filament resources instead and reserve Filament One for settings, profiles, and similar focused pages. You can use both patterns in the same admin panel where each fits.