Weave Code
Admin Ui Laravel Package
ibexa/admin-ui
Ibexa Admin UI provides the Back Office interface for Ibexa DXP, bundling the templates, assets, and configuration needed to run and extend the admin panel. Part of Ibexa DXP; install via the official guide.
At a glance
Frequently asked questions about Admin Ui
- Can I use Ibexa Admin UI in a standalone Laravel project without Ibexa DXP?
- No, this package is tightly coupled with Ibexa DXP’s backend APIs (e.g., NodeFactory, Symfony bundles). You’d need to abstract Ibexa’s logic via a facade or API layer (e.g., REST/GraphQL) to integrate it with Laravel, which requires significant refactoring.
- What Laravel versions does Ibexa Admin UI support?
- While Ibexa DXP (Symfony 7.4) underpins this UI, Laravel 10+ can technically integrate with it via Symfony bridges (e.g., `symfony/http-client`). However, full compatibility depends on aligning Symfony components and may require custom middleware or container adjustments.
- How do I install Ibexa Admin UI in a Laravel project?
- You cannot install this package directly via Composer without Ibexa DXP. First, install Ibexa DXP as per [official docs](https://doc.ibexa.co/en/latest/install/), then include this bundle in your Ibexa project. For Laravel integration, you’d need to proxy Ibexa routes or use its headless API.
- Does Ibexa Admin UI work with Laravel’s frontend stacks (e.g., Livewire, Inertia.js)?
- The UI uses React-like JS components (ES6+) and Webpack Encore. To integrate with Laravel, isolate Ibexa’s frontend in a micro-frontend (e.g., iframe) or rewrite components to use Laravel’s frontend stack (e.g., Livewire for reactivity or Inertia.js for Vue/React).
- Are there alternatives to Ibexa Admin UI for Laravel admin panels?
- Yes. For Laravel-native solutions, consider Filament, Nova, or Backpack for CRUD interfaces. If you need Ibexa-specific features, evaluate its headless API with a separate frontend (e.g., Next.js) instead of bundling the full UI.
- How do I handle Ibexa’s Doctrine ORM data in Laravel’s Eloquent?
- Ibexa uses Doctrine, while Laravel uses Eloquent. To sync data, create custom mappers or read models to translate Ibexa entities (e.g., `Node`) into Eloquent models. For write operations, use Ibexa’s API or a facade layer to abstract database interactions.
- What’s the licensing impact of using Ibexa Admin UI in a commercial Laravel app?
- This package is dual-licensed under GPLv2 (copyleft) and Ibexa BUL (commercial). GPL restricts redistribution; Ibexa BUL requires a valid DXP subscription. Review [Ibexa’s licensing terms](https://www.ibexa.co/licenses) and consult legal to ensure compliance, especially if modifying or redistributing.
- Can I customize Ibexa Admin UI’s styling or components for Laravel?
- Yes, but changes must align with Ibexa’s extensibility guidelines. Override Twig templates, SASS variables, or JS components via Ibexa’s [extending docs](https://doc.ibexa.co/en/4.4/extending/). For Laravel-specific tweaks, isolate customizations in a micro-frontend or use Laravel Mix/Vite to rebuild assets.
- How do I test Ibexa Admin UI in a Laravel environment?
- Test via Ibexa’s built-in tools (e.g., PHPUnit for backend logic, Cypress for frontend). For Laravel integration, mock Ibexa’s API responses (e.g., with `Mockery` or `Pest`) and test your facade layer. Ensure Symfony components (e.g., `symfony/ux`) are compatible with Laravel’s testing stack.
- What are the production concerns when deploying Ibexa Admin UI with Laravel?
- Key concerns include: asset optimization (replace Webpack Encore with Laravel Mix/Vite), route conflicts (proxy Ibexa routes via Laravel middleware), and performance (cache Ibexa API calls or use a CDN for static assets). Monitor Symfony/Laravel version skew and Ibexa’s roadmap for breaking changes.
Weaver
How can I help you explore Laravel packages today?