Weave Code
Installer Bundle Laravel Package
sylius/installer-bundle
Sylius Installer Bundle provides a command-line installer for Sylius applications, checking environment requirements, configuring database and mailer settings, creating an admin user, and optionally loading sample data.
Web and command line installer for Sylius.
Frequently asked questions about Installer Bundle
- Can I install sylius/installer-bundle in a Laravel application?
- No. It is a Symfony bundle whose services, routes, commands, and event subscribers expect the Sylius and Symfony runtime, so Composer resolution and container wiring will conflict with a Laravel app. The only viable topology is a separate Sylius runtime integrated over HTTP or queues.
- What does sylius/installer-bundle actually do?
- It provides the first-run installer for Sylius applications, available through both a web wizard and console commands. It checks environment requirements, configures database and mailer settings, creates an admin user, and can optionally load sample data and install assets.
- Is sylius/installer-bundle compatible with Laravel?
- No. The package targets Symfony's kernel, DI container, routing, Twig, and console, and it calls Sylius core services that do not exist in Laravel. It does not use Laravel's service container, Artisan, Blade, or Eloquent.
- How do I build a first-run setup wizard in Laravel instead?
- Use native Laravel tools: an Artisan command such as app:install, Laravel Prompts for interactive questions, migrations and seeders for schema and data, and config or environment writes for database and mailer settings. Add prerequisite checks and make each step idempotent so reruns are safe.
- Which Laravel versions does sylius/installer-bundle support?
- None. It is not a Laravel package and publishes no Laravel version constraints; its compatibility is tied to Sylius and Symfony releases. Do not plan around Laravel version support for this package.
- How do I install sylius/installer-bundle?
- Install it with Composer inside a Sylius application, then enable the bundle in the Symfony kernel and use the Sylius installer flow. It is normally pulled in through the Sylius platform rather than added to a Laravel project.
- Can I reuse sylius/installer-bundle code in a Laravel project?
- The license is MIT, so you can read and adapt the source legally, but the code本身 will not run in Laravel. The reusable asset is the pattern: gated prerequisite checks, idempotent and resumable setup steps, and one shared service layer behind both web and CLI front ends.
- Why does sylius/installer-bundle show zero stars or dependents?
- Those numbers are artifacts of Sylius's monorepo split and do not prove abandonment. The bundle reaches most users through sylius/sylius, so verify release cadence and support against the main Sylius repository and Packagist download stats.
- What are the Laravel alternatives to sylius/installer-bundle?
- For Laravel, use php artisan migrate --seed, Laravel Prompts for interactive setup, a custom app:install command, and Forge, Envoy, or Docker for provisioning. These are the native equivalents and integrate with Laravel's container, config, and database layers.
- What production concerns should I check before using sylius/installer-bundle?
- Treat it as part of a separate Sylius platform with its own Composer root, database, CI, and deployment pipeline. Lock or disable the installer after setup, protect admin creation and database credentials, and make setup steps idempotent to avoid partial reruns.
Weaver
How can I help you explore Laravel packages today?