Weave Code
Ibexa Dataflow Bundle Laravel Package
code-rhapsodie/ibexa-dataflow-bundle
Integrates Code Rhapsodie Dataflow Bundle into Ibexa 4.0+ to manage content imports from external sources. Provides a backoffice UI to create and schedule dataflow processes (one-off or recurring) with per-type options.
Import / export bundle for Ibexa Content based on Code Rhapsodie Dataflow framework
Frequently asked questions about Ibexa Dataflow Bundle
- What Laravel versions does this package support?
- This package is designed for Ibexa 4.0+ (not Laravel directly), which typically integrates with Symfony 5+. Ensure your Ibexa DXP 5.x environment aligns with the supported stack. Laravel compatibility depends on your Ibexa setup, as Ibexa itself may use Laravel components internally.
- How do I install and configure this bundle for Ibexa?
- Run `composer require code-rhapsodie/ibexa-dataflow-bundle`, enable both `CodeRhapsodieDataflowBundle` and `CodeRhapsodieIbexaDataflowBundle` in `config/bundles.php`, import the routing file, and update the database schema via the Dataflow Bundle’s guide. Ensure the Dataflow bundle loads first.
- Can I schedule recurring dataflow jobs in Ibexa’s backoffice?
- Yes, the bundle provides a UI to create one-off or recurring workflows. Define the first run date/time and interval (e.g., daily/weekly) directly in the Ibexa backoffice for automated content imports.
- Does this bundle support Ibexa 6.x or only 5.x?
- Currently, this bundle is maintained for Ibexa 5.x only. Check the [compatibility table](https://github.com/code-rhapsodie/ibexa-dataflow-bundle) for updates on Ibexa 6.x support, as it’s not officially listed yet.
- What happens if I accidentally delete a pending job?
- The delete button lacks confirmation dialogs or audit logs by default, so accidental deletions could remove in-progress jobs. Review workflows before deleting and consider customizing the UI to add safeguards (e.g., modal confirmations).
- Can I use this bundle for CLI-only dataflow execution?
- Yes, but the backoffice UI is optional. For CLI use, follow the [Dataflow Bundle’s queue setup](https://github.com/code-rhapsodie/dataflow-bundle#queue) and replace `--connection` with `--siteaccess` in commands (except `dump-schema`).
- Are there alternatives to this bundle for Ibexa imports?
- Native Ibexa tools like the [Import/Export API](https://doc.ibexa.co/en/latest/guides/content_management/import_export/) or third-party bundles (e.g., `ezsystems/ezplatform-import-export`) may suffice for basic needs. This bundle excels for scheduled, complex ETL workflows with UI management.
- How do I restrict access to the dataflow UI?
- Use Ibexa’s default RBAC (Role-Based Access Control) to limit visibility. The bundle doesn’t introduce new permissions, so configure roles in Ibexa’s admin panel to control who sees the workflow UI or delete buttons.
- Will this bundle work with custom DataflowTypes?
- Yes, the bundle preserves extensibility. Your existing `DataflowTypes` will work unchanged, and you can add new ones without modifying the bundle’s core logic. Test custom types post-installation to confirm compatibility.
- How do I test dataflow jobs before deploying to production?
- Use the backoffice UI to create test workflows with small datasets. Monitor job logs in Ibexa’s default logging system (e.g., `var/log/`) and validate outputs in the Ibexa content structure. Avoid production data during testing.
Weaver
How can I help you explore Laravel packages today?