Weave Code
Ibexa Dataflow Bundle Laravel Package
code-rhapsodie/ibexa-dataflow-bundle
Ibexa Dataflow Bundle integrates Code Rhapsodie Dataflow into Ibexa 4.0+ backoffice, letting you create and schedule content import workflows from external sources. Run imports once or at recurring intervals, with UI-based management and CLI support.
At a glance
Frequently asked questions about Ibexa Dataflow Bundle
- What is code-rhapsodie/ibexa-dataflow-bundle used for?
- It integrates Code Rhapsodie Dataflow Bundle into Ibexa 4.0+ to manage content imports from external sources. It adds a backoffice UI to create, configure, and schedule one-off or recurring dataflow processes per DataflowType. Typical uses include content migration, synchronization, and bulk imports from CSV, APIs, or databases.
- How do I install code-rhapsodie/ibexa-dataflow-bundle?
- Require it with Composer, enable CodeRhapsodieDataflowBundle before CodeRhapsodieIbexaDataflowBundle in config/bundles.php, import the bundle routing file, update the database schema per the Dataflow Bundle guide, and schedule the job runner. Loading order matters because Dataflow must load first. Follow the README steps for routing and schema.
- Does code-rhapsodie/ibexa-dataflow-bundle support Ibexa 4.0 and 5.x?
- The README compatibility table lists Ibexa Dataflow 6.x as maintained for Ibexa Content 5.x. The overview says Ibexa 4.0+, but backward compatibility with Ibexa 4.x is not guaranteed per the README table. Check the version matrix before upgrading.
- How do I schedule recurring dataflow jobs in Ibexa Dataflow?
- The backoffice UI lets you set a process to run once at a given date and time or regularly by defining the first run and interval. You still need to schedule the Dataflow job runner as described in the Code Rhapsodie Dataflow Bundle queue section. Use Symfony Messenger for async execution.
- What queue setup does code-rhapsodie/ibexa-dataflow-bundle require?
- It relies on Symfony Messenger for async job execution, so you must configure a transport such as Doctrine, Redis, or RabbitMQ and run workers. Poor queue configuration can cause job failures, so monitor workers and job history. Refer to the Dataflow Bundle queue documentation.
- Can I use code-rhapsodie/ibexa-dataflow-bundle in a Laravel application?
- No native Laravel integration exists; the bundle is built as a Symfony bundle for Ibexa CMS. Laravel developers evaluating ETL options should use the underlying Code Rhapsodie Dataflow Bundle or a Laravel-native queue and import package. The Ibexa bundle depends on Ibexa 5.x and its content repository.
- How do I create a custom DataflowType for Ibexa imports?
- Extend AbstractDataflowType and register your type as a DataflowType service so it appears in the backoffice UI. The plugin-based architecture supports custom sources such as APIs, CSV, or databases. You can then set per-type options when creating a process.
- What permissions are needed for the Ibexa Dataflow backoffice UI?
- The bundle adds an admin section under Ibexa Dataflow, which may require custom roles for non-admin users. Review and adjust Ibexa permissions so content editors or operators can manage schedules without full admin access. Test role assignments in staging.
- How does code-rhapsodie/ibexa-dataflow-bundle handle content publishing and users?
- By default the ContentWriter publishes content using the admin user. The README notes you can configure another user if needed. Plan user permissions carefully for imports and publishing.
- What are alternatives to code-rhapsodie/ibexa-dataflow-bundle for Ibexa imports?
- Consider Ibexa native import and export tools such as ezplatform-content-import, or the standalone Code Rhapsodie Dataflow Bundle without the Ibexa UI. Third-party automation tools may fit simpler sync workflows. Evaluate queue, custom field support, and maintenance needs.
Weaver
How can I help you explore Laravel packages today?