Weave Code
System Info Laravel Package
ibexa/system-info
Ibexa System Info is an Ibexa DXP bundle that surfaces details about the system your DXP runs on, giving system administrators and Support engineers quick diagnostic insight. Requires an Ibexa DXP installation.
Providing information about the system Ibexa is running on, and Ibexa install itself
Frequently asked questions about System Info
- Can I use ibexa/system-info in a Laravel application?
- No. ibexa/system-info is a Symfony bundle that ships as part of the Ibexa DXP bundle set and binds directly to Ibexa core internals such as repository configuration providers, core schema table names and Twig components. It has no meaning outside an Ibexa DXP kernel, so there is no port path to Laravel. If you only want the pattern, reimplement a small read-only diagnostics panel in Laravel rather than pulling this package in.
- How do I install ibexa/system-info?
- In practice you do not install it directly: it arrives transitively through the Ibexa DXP metapackage, so integration is verification and access control rather than development. Confirm it is present with composer show ibexa/system-info and make sure the bundle is registered in your kernel. If you run a custom build that omits it, add the version pinned to your DXP major rather than the latest tag.
- Which Ibexa DXP and PHP versions does ibexa/system-info support?
- The package follows a dual release train: the 4.6.x line maps to Ibexa DXP 4.6, and the 5.0.x line maps to Ibexa 5. The 5.x line requires PHP 8.3 or newer and Symfony 6 or 7, plus the newer twig-components package from 5.0.10 onward. Mixed-version fleets need per-environment validation because the collectors track the schema of the matching core release.
- What does the Ibexa System Information panel actually report?
- It registers a System Information admin panel backed by collectors that surface the PHP version, runtime environment, installed packages, service-life and version data, and repository configuration. The output is designed for system administrators and Ibexa Support engineers doing quick diagnostics rather than for application features. Treat the output as sensitive: it exposes stack and configuration detail by design, so consider a redaction or export step before sharing it outside your organisation.
- How do I control who can view the System Information tab?
- Access is governed by Ibexa permission policies, not by the bundle itself, so a misconfigured policy turns a support aid into reconnaissance material. Restrict the tab to a small administrative or support role and verify the restriction in each environment rather than assuming it. Review the policy whenever you add roles or expose a new admin hostname.
- Is ibexa/system-info licensed under the GPL or the Ibexa Business Use License?
- It is dual licensed: the Ibexa Business Use License version 2.4 or later, granted by a valid Ibexa DXP subscription, or the GNU General Public License version 2. The NOASSERTION value you see in metadata reflects exactly that ambiguity, and it is the highest-impact unknown for the package. Have legal confirm which applies to your deployment before you fork, modify or redistribute anything.
- Is ibexa/system-info already installed in my Ibexa DXP project?
- Almost certainly yes, because it is a bundled component of the DXP metapackage and only has three stars and zero dependents, meaning nobody adopts it as a destination package. Run composer show ibexa/system-info and check your kernel bundle registration and admin route to confirm. The real decision is therefore your Ibexa major version, which you have already made elsewhere.
- Can I add custom collectors to ibexa/system-info?
- Custom collectors are technically possible because the bundle is built around collector classes, and teams sometimes add their own infrastructure metadata, but every collector is fragile against Ibexa core changes. For most installations the stock output is sufficient for support tickets, so weigh the maintenance cost before adding anything. If you do extend it, cover the custom code with your own checks because external scrutiny of this package is minimal.
- Will upgrading Ibexa DXP break ibexa/system-info?
- Expect breakage at each DXP major upgrade. Historical fixes show version detection breaking after a package rename, table names being realigned to a new core schema, and content type version columns being renamed. Pin the branch that matches your DXP major and re-verify the panel after every upgrade rather than relying on the previous output.
- What should I use instead if I am not running Ibexa DXP?
- For Laravel, look at Laravel Telescope, Laravel Pulse, Laravel Debugbar or spatie/laravel-health for environment and diagnostics visibility. For plain Symfony, the framework profiler and a small custom controller cover the same ground. The transferable idea here is a read-only diagnostics panel exposed to admins and support, which is small to build and does not justify coupling your application to Ibexa internals.
Weaver
How can I help you explore Laravel packages today?