Weave Code
Core Laravel Package
ibexa/core
Ibexa Core is the foundation of the Ibexa Digital Experience Platform, delivering the content repository, public PHP APIs, and MVC layers needed to build and manage enterprise content applications on Symfony.
Ibexa Core is the foundational package of the Ibexa DXP, providing the shared services, APIs, and Symfony bundles that power content management applications. It supplies the content repository, dependency injection configuration, and extension points used by Ibexa’s CMS and commerce products.
- Content repository with versioning, drafts, and publishing workflows
- Flexible content modeling and multi-language support
- Role-based permissions and user management
- Symfony integration for bundles, services, and configuration
- Extensible APIs for headless and custom applications
Frequently asked questions about Core
- Can I install ibexa/core in a Laravel application with Composer?
- You can add the package with Composer, but it is not designed to run inside a Laravel application. ibexa/core is the kernel bundle of Ibexa DXP and expects to own the Symfony application, service container, routing, Doctrine mappings, and request lifecycle. For a Laravel codebase, run Ibexa as a separate service and integrate over HTTP instead of embedding it.
- What does ibexa/core actually provide?
- It provides the foundational platform services behind Ibexa DXP: the content repository and Public API, content model and field types, multilingual and siteaccess routing, permissions, binary and IO storage, search integration, Twig rendering helpers, and notifications. It is a kernel bundle for a full DXP, not a small composable library. Plan around it as an application platform.
- Is ibexa/core a good fit for a Laravel project?
- Only as an adjacent application behind an API boundary, not as a Composer dependency. Its architecture assumes it is the Symfony 7.x application and does not compose cleanly inside Laravel's container or lifecycle. If you need DXP capabilities, treat Ibexa as a bounded context that owns content and search while Laravel owns accounts, transactions, and the customer-facing product.
- Which PHP and Symfony versions does ibexa/core support?
- The upstream CI tracks PHP 8.3 and 8.4 with Symfony 7.4 LTS, so pin your runtime to match. Do not assume database, Solr, or Elasticsearch versions; validate them against the supported matrix for your Ibexa edition. Laravel version support is not applicable because the package is not a Laravel library.
- What license does ibexa/core use, and can I use it commercially?
- The package reports NOASSERTION, and Ibexa ships a GPL community edition plus a commercial edition with different obligations. Treat licensing as a blocking decision before engineering work. Confirm with counsel which edition applies and what it means for your distribution and support model.
- How do I integrate Ibexa DXP with a Laravel application?
- Stand up the ibexa/oss or ibexa/dxp skeleton as its own application, not the bare ibexa/core package. Integrate through Ibexa's REST or GraphQL surface, or a thin backend-for-frontend, and never read its Doctrine tables directly. Prove public API reads and writes, one custom field type, and one search aggregation in a short spike before committing.
- Do I need Solr or Elasticsearch to use ibexa/core?
- Search integration is part of the platform, and Solr or Elasticsearch is typically part of a realistic Ibexa deployment. Whether it is mandatory depends on your content volumes, search features, and the supported matrix for your edition. Validate the search backend and version during the spike rather than assuming a database-only setup.
- Can I use ibexa/core as a headless CMS behind a Laravel API?
- Yes, that is the realistic integration shape: Ibexa owns content storage, editorial workflow, and search indexing, while Laravel serves the customer-facing product. Expose content through REST, GraphQL, or a BFF rather than embedding the kernel. Confirm that you can export content through the Public API if you need an exit path.
- How hard is upgrading Ibexa from 4.6 to 5.0?
- Upstream maintains parallel 4.6.x and 5.0.x trains, with fixes backported across majors, so documentation and triage are split. If you board at 5.0.x, ask what the true 4.6 to 5.0 upgrade cost would be for your integrations and custom field types. Budget for testing public API criteria, serializer factories, siteaccess matchers, notification renderers, and IO handlers.
- Is ibexa/core actively maintained, and what alternatives should I consider for Laravel?
- The repository appears to be a split or mirror of a commercially developed product, so star counts and listed dependents are not reliable adoption signals. Verify the live release feed and cadence rather than trusting a single scraped release date. For Laravel-first teams, compare a dedicated headless CMS or API-first content service before adopting a full DXP.
Weaver
How can I help you explore Laravel packages today?