Weave Code
Post Install Laravel Package
ibexa/post-install
Ibexa Post Install Tool is a Composer utility that runs post-installation setup tasks for Ibexa DXP projects, automating configuration and scripted steps after dependencies are installed.
Post Installation Tool for Ibexa products
Frequently asked questions about Post Install
- Can I use ibexa/post-install in a Laravel application?
- No, not as a runtime dependency. ibexa/post-install is an Ibexa DXP (formerly eZ Platform) deployment and operations support package with no Laravel service provider, no Laravel configuration surface, and no runtime API intended for application code. It is technically installable via Composer, but it would only add Symfony console and deployment code plus Ibexa-specific configuration without giving your Laravel app any value. For a Laravel-only project, treat it as reference material for infrastructure patterns rather than something you install.
- What does the Ibexa Post Install Tool actually do after composer install?
- It automates routine post-install setup tasks for Ibexa DXP projects so you can move from a fresh dependency install to a working environment with minimal manual work. It integrates with Composer scripts and covers deployment-oriented concerns such as install command behavior, Ibexa Cloud and Platform.sh configuration, vhost templates, Varnish VCL, and Solr schema files. In short, it removes repetitive bootstrapping steps that would otherwise be done by hand after dependencies are installed.
- How do I install ibexa/post-install via Composer?
- It is installed with Composer inside an Ibexa DXP project and is normally pulled in as part of the platform's expected deployment tooling, then triggered through Composer scripts. Version alignment matters more than the install command itself, so match the package line to your Ibexa DXP release rather than picking the latest tag. Do not add it to a Laravel application just to see what it does; use a throwaway Ibexa environment instead.
- Which Laravel and Symfony versions does ibexa/post-install support?
- There is no Laravel version support because this is not a Laravel package. The 5.0 line targets Symfony 7.4 LTS era components and aligns with Ibexa DXP 5.x, while the 4.6.x line aligns with Ibexa DXP 4.6. Laravel uses Symfony components internally but not the full Symfony framework, so console commands and deployment hooks written for Ibexa DXP are not a supported combination with a Laravel runtime.
- What license does ibexa/post-install use, Ibexa BUL or GPL-2.0?
- It is dual licensed. The README offers the Ibexa Business Use License (Ibexa BUL) version 2.4 or later, which is granted through a valid Ibexa DXP subscription, and alternatively GNU GPL version 2. GitHub reports the license as NOASSERTION, so tooling will not resolve it automatically. GPL-2.0 is copyleft and can create obligations if code is linked, modified, or distributed with proprietary software, so any reuse in a commercial Laravel product needs legal review before adoption.
- Is ibexa/post-install actively maintained and safe for production?
- Maintenance is tied to Ibexa DXP releases rather than independent community activity, and the public signals are thin: around 8 stars, zero dependents, and releases that frequently state no significant changes. That means limited external testing and weak independent support signals, so you should not assume broad community validation. It is reasonable in production only inside a supported Ibexa DXP deployment where Ibexa provides the upgrade and security path.
- What deployment artifacts does ibexa/post-install provide?
- The package carries infrastructure and deployment artifacts rather than application features. That includes install command behavior, Ibexa Cloud and Platform.sh service configuration, vhost templates, Varnish VCL, and Solr schema files. If you only need one of those pieces, extract and adapt that specific artifact into your own infrastructure-as-code repository instead of taking a dependency on the whole package.
- What are the alternatives to ibexa/post-install for a Laravel project?
- For a Laravel-only project the practical alternative is to skip the package entirely and use Laravel-native deployment tooling such as Forge, Envoyer, Laravel Cloud, or Deployer scripts. If you specifically want the hosting patterns, copy the relevant vhost, Varnish, Solr, or Platform.sh configuration into your own repository with attribution and a license review. There is no Laravel-facing equivalent because the problem it solves is Ibexa DXP bootstrapping, not Laravel application setup.
- How should I test or evaluate ibexa/post-install before adopting it?
- Run a short, time-boxed spike in a disposable Ibexa DXP environment rather than inside your Laravel application, so you can see the actual post-install behavior and Composer script wiring. Confirm which artifact you need, then confirm the license path with legal before any code is reused. If the spike shows you only need vhost, VCL, or Solr patterns, close the evaluation and port those files into your own repo.
- Does ibexa/post-install work with Ibexa DXP 4.6 and 5.0?
- The package is versioned in lockstep with Ibexa DXP, with a 4.6.x line and a 5.0.x line that targets Symfony 7.4 era components. You must align the package version to your exact DXP release, because drift between the two can break installation and deployment hooks. Before committing, confirm the supported upgrade path and security maintenance commitment from Ibexa for the line you plan to run.
Weaver
How can I help you explore Laravel packages today?