- What is filagora/filagora-core used for?
- Filagora Core is the shared foundation package for the Filagora ecosystem. It provides the module registry, settings support, contracts, base models, and common services that other Filagora Filament packages build on. You normally install it as part of a modular Filagora marketplace setup rather than as a standalone feature package.
- Do I need filagora/filagora-core if I only use one Filagora module?
- You may still need it because Filagora modules can depend on core contracts and shared services at runtime. Composer will usually pull filagora/filagora-core in automatically when another Filagora package requires it. If your chosen module has no dependency on core, you can follow that package's own installation instructions instead.
- How do I install filagora/filagora-core in a Laravel application?
- Install it with Composer using the package name filagora/filagora-core, typically alongside the Filagora Filament modules you plan to use. Because it is a shared foundation, let Composer resolve it as a dependency where possible rather than forcing a mismatched version. Check the package README for any service provider registration or configuration publishing steps required by your Laravel version.
- Which Laravel versions does filagora/filagora-core support?
- Filagora Core is built for Laravel applications and is intended to match the Laravel and PHP constraints required by the Filagora modules you install. The authoritative compatibility details are in the package composer.json and release notes. Review those constraints before upgrading Laravel or deploying to an older PHP runtime.
- How does the module registry in Filagora Core work?
- Filagora Core provides a module registry so Filagora packages can register themselves and expose shared behavior consistently. This keeps marketplace features modular, with modules depending on core contracts instead of tightly coupling to each other. Consult the Filagora documentation for the exact registration and discovery API used by your package versions.
- Where are Filagora settings stored and how do I configure them?
- Filagora Core includes shared settings support so configuration can be handled consistently across Filagora modules. The exact storage mechanism and any publishable configuration files should be confirmed in the package documentation for your installed version. Treat these settings as application configuration and avoid hard-coding values inside individual modules.
- Can I extend Filagora base models and contracts in my own application?
- Yes, the package is designed around shared contracts, base models, and common services that other Filagora modules build on. You can extend the provided base classes and implement the contracts in your own code where the package allows it. Review backwards compatibility notes before upgrading core, since shared foundations can affect multiple modules at once.
- Is filagora/filagora-core compatible with Filament panels?
- Filagora is a set of Filament-oriented packages, and filagora-core is the shared foundation rather than the admin UI itself. It supplies contracts, models, settings, and services that the Filament-facing Filagora modules use inside your panels. Install the relevant Filagora Filament packages alongside core to get the actual panel resources and pages.
- How should I test a Laravel app that depends on Filagora Core?
- Test your integrations with Laravel's normal testing tools and a dedicated test database or in-memory connection. If you are building a Filagora-compatible package, use Orchestra Testbench to boot the package in a minimal Laravel application. You can also bind or mock core contracts in the container to isolate your module tests from shared services.
- Is Filagora Core production-ready and how is it maintained?
- Filagora Core is intended as the stable shared foundation for the Filagora marketplace modules, so production suitability depends on the specific Filagora package versions you deploy. Pin versions in composer.json, read changelogs before upgrading, and test upgrades in staging. Confirm the repository activity and support channels for your version before adopting it in a critical application.