Technical Evaluation

Purpose Alignment: Remains exclusively Ibexa DXP-focused with no generic Laravel applicability. New features (e.g., IBX-5798 headless regression tests, ibexa/behat integration) further cement Ibexa-specific coupling.
- Visual testing (PR #63) and search indexing separation (PR #67) are Ibexa DXP workflows (e.g., Elasticsearch integration).
- Edition-based CLI logic (PR #71) and Ibexa Cloud vs. self-hosted exclusions (e.g., IBX-4516) are incompatible with Laravel’s architecture.
Laravel Compatibility: 0%. Key additions:
- Hard PHPUnit9 dependency (PR #69/#70) conflicts with Laravel’s flexible PHPUnit versions.
- Node.js 18 + PHP 8.1/8.2 enforcement (PR #75) is redundant for Laravel (already supported) but ties to Ibexa’s stack.
- ibexa/behat and ibexa/docker (PR #73) remain Laravel-incompatible.
Core Functionality Updates:
- Visual regression testing (Percy/Applitools) could inspire Laravel’s Laravel Dusk + Storybook, but implementation is Ibexa-specific.
- Search indexing separation (PR #67) mirrors Laravel Scout’s indexing, but Ibexa’s Elasticsearch setup is monolithic.
- Git safety directives (PR #74) are niche; Laravel uses .gitignore/composer.json instead.

Direct Integration: Still infeasible. New features deepen Ibexa dependency:
- Headless regression tests (IBX-5798) require Ibexa’s API clients.
- ibexa/docker installation (PR #73) assumes Ibexa’s Symfony bundle structure.
Indirect Use Cases:
- CI/CD Templates: GitHub Actions workflows (e.g., parallel PHPUnit, Node.js 18) can be partially adapted (e.g., Laravel’s phpunit.xml parallelization).
- Visual Testing: Ibexa’s Percy integration could inspire Laravel’s Dusk + Percy, but requires rewriting.
- Dependency Management: Logic for edition-based exclusions (PR #71) might inform Laravel’s conditional composer packages (e.g., config/editions.php).
Blockers (Updated):
- Licensing: Dual license (GPL-2.0/Ibexa BUL) still restricts commercial use without Ibexa DXP subscription.
- Tight Coupling: New features (e.g., IBX-5798) assume Ibexa’s Symfony bundles, database schemas, and workflows.
- PHPUnit9 Pinning: Hard dependency (PR #69/#70) conflicts with Laravel’s flexibility.

Risk Area	Severity	Mitigation Strategy	Update
Architectural Mismatch	Critical	Avoid direct integration.	Worsened: New Ibexa-specific features (e.g., `IBX-5798`) increase gap.
Dependency Conflicts	High	Isolate Ibexa packages in a separate repo.	New: PHPUnit9 hard pinning (PR #69/#70) adds conflict risk.
Licensing Compliance	High	Requires Ibexa DXP subscription.	Unchanged.
Maintenance Overhead	Medium	Ibexa’s active development may break Laravel.	Increased: More Ibexa-specific PRs (e.g., `ibexa/behat` in PR #73).
Testing Gaps	Medium	Laravel lacks Ibexa’s Behat/visual ecosystem.	New: Visual testing (PR #63) highlights Laravel’s missing tools.

Why Ibexa DXP?
- Updated: New features (e.g., IBX-5798 headless tests) strengthen Ibexa’s justification for migration.
- If not migrating, which specific Ibexa features (e.g., visual testing, parallel CI) are needed for Laravel?
Alternatives for Laravel
- Updated:
  - Visual Testing: Replace Ibexa’s Percy with Laravel Dusk + Storybook.js.
  - Search Indexing: Use Laravel Scout (Elasticsearch/Algolia) instead of Ibexa’s monolithic setup.
  - CI/CD: Leverage Laravel Forge, Portainer, or custom GitHub Actions (no Ibexa dependency).
Customization Feasibility
- Updated:
  - Forking: Still not viable. New features (e.g., ibexa/behat in PR #73) are Ibexa-exclusive.
  - Script Extraction: Possible for CI templates (e.g., parallel PHPUnit), but requires rewriting Ibexa logic (e.g., IBX-5798 tests).
Licensing Impact
- Unchanged: Dual license still requires Ibexa DXP subscription for commercial use.
Performance/Scaling
- Updated:
  - Ibexa’s PHPUnit9 pinning (PR #69/#70) may slow Laravel’s CI if adopted.
  - Node.js 18 enforcement (PR #75) is redundant for Laravel but adds version lock-in.

Integration Approach

Direct Fit: 0% (Ibexa DXP only).
Partial Fit: 20% (CI/CD templates, PHPUnit/Node.js tooling).
- Compatible Layers:
  - PHP 8.1–8.2 and Node.js 18 support (PR #75).
  - GitHub Actions workflows (adaptable to Laravel).
  - Composer dependency logic (e.g., install vs. update in PR #68).
- Incompatible Layers:
  - Ibexa-specific testing (ibexa/behat, IBX-5798).
  - Symfony bundles (JsRoutingBundle, EzPublishCoreBundle).
  - Database schemas (Ibexa’s ezpublish tables vs. Laravel’s migrations).

Step	Action	Tools/Dependencies	Risk	Update
1	Assess Needs	Audit Laravel CI/CD gaps.	Low	New: Focus on visual testing (PR #63) or parallel PHPUnit (PR #68).
2	Extract CI Templates	Fork `ibexa/ci-scripts`; remove Ibexa code.	Medium	Harder: New features (e.g., `IBX-5798`) require more rewrites.
3	Adapt for Laravel	Replace `ibexa/behat` → `pestphp/pest`.	High	New: Ibexa’s visual testing (PR #63) needs Dusk + Percy rewrite.
4	Test in Isolation	Run in Laravel Docker (e.g., `laradock`).	Medium	New: PHPUnit9 pinning (PR #69/#70) may break Laravel’s CI.
5	Integrate Selectively	Use only PHPUnit parallelization.	Low	Limited: Most features are Ibexa-specific.

Composer: Worse.
- New: PHPUnit9 hard pinning (PR #69/#70) conflicts with Laravel’s flexible PHPUnit versions.
- Workaround: Use composer.json overrides or vendor patching.
PHP Extensions: Unchanged (PHP 8.1+ supported by Laravel 9+).
Docker: Still incompatible.
- Ibexa’s Docker setup (PR #73) is Symfony-centric → not drop-in for Laravel.
- Alternative: Use laradock or customize Ibexa’s Dockerfile (high risk).
Testing Frameworks: Still incompatible.
- Behat (PR #73) is Ibexa-specific → replace with Pest/Dusk.
- Visual testing (PR #63) requires Percy/Applitools