Weave Code
Installer Laravel Package
lara-zeus/installer
Lara Zeus Installer provides a streamlined way to install and configure Lara Zeus packages in your Laravel application, simplifying setup steps so you can get the ecosystem running quickly with minimal manual configuration.
filament application installer
Frequently asked questions about Installer
- What is lara-zeus/installer used for?
- lara-zeus/installer is a scaffolding and CLI tooling package that installs and configures Lara Zeus packages, including Filament panels, in a Laravel application. It runs once during project bootstrap or when adding a panel, publishing the required config, assets, and scaffolding, then becomes inert. It is not a runtime library, so it adds no request-path coupling or service-provider surface to your application.
- How do I install lara-zeus/installer in a Laravel project?
- Add it with Composer, preferably as a dev dependency using composer require --dev lara-zeus/installer. Then run the console command the package provides to publish and configure the Lara Zeus and Filament scaffolding. Run it on a disposable branch first and review the resulting diff before committing anything.
- Should lara-zeus/installer be a require-dev or a require dependency?
- It belongs in require-dev because it is install-time tooling, not application runtime code. Keeping it out of production dependencies avoids shipping a scaffolder to your servers and keeps the deployed vendor tree leaner. Application code should never reference the installer at runtime.
- Which Laravel versions does lara-zeus/installer support?
- Release 1.0.1 mentions Laravel 13 alongside documentation updates, but the changelog alone does not confirm whether that reflects a tested CI matrix or a docs mention. Check the illuminate and laravel/framework constraints in composer.json at the tag before assuming support. Pin the version you have actually validated rather than relying on a floating ^1.0 constraint.
- Is lara-zeus/installer safe to re-run on a project that already has Filament installed?
- Idempotency and overwrite behaviour are not documented in the 1.0.1 release notes, so treat them as unverified. Test a re-run on a scratch application before pointing it at a project with an existing Filament panel, and check whether published config or asset files get replaced. Take a commit or backup first so you can review and revert any destructive changes.
- What files does lara-zeus/installer publish into my Laravel app?
- It publishes Filament configuration, assets, and user-model scaffolding into the conventional config, public, and app locations, along with any Lara Zeus package config. Because stub templates can change between releases, even ones labelled as typo fixes, always diff the generated output. Stub drift alters what the installer produces without showing up in the changelog.
- Should I pin lara-zeus/installer to an exact version?
- Yes. The package is at 1.0.x with a single-maintainer bus factor, and a patch release already expanded its framework compatibility claim. Pin to an exact version such as 1.0.1 rather than ^1.0 so a future patch cannot silently change scaffold output. Bump deliberately after reviewing the diff on a scratch project.
- What happens if lara-zeus/installer fails partway through an install?
- Failure behaviour on partially completed installs is not documented, so assume it may leave the project half-scaffolded. Run it in a throwaway branch or a scratch clone so a failed run costs nothing. If it aborts mid-way, discard the branch and start clean rather than patching the partial output by hand.
- Can I run lara-zeus/installer in CI or a production deployment?
- You should not. It is a one-time developer bootstrap tool, not a deployment step, and running it in production could rewrite published config or assets on live hosts. Keep it in require-dev, run it locally, and commit the generated files to version control so your normal pipeline ships the committed output.
- Is lara-zeus/installer actively maintained, and what are the alternatives?
- It is early-life software at 1.0.x with a small maintainer base, so plan a contingency. The generated scaffolding lives in your repository, which means you can drop the installer entirely once setup is complete. Alternatives include Filament's own install command plus manual publishing of Lara Zeus package configs, and pinning the version limits your exposure if the package stalls.
Weaver
How can I help you explore Laravel packages today?