Weave Code
Nova Data Sync Laravel Package
coreproc/nova-data-sync
A Laravel Nova package for syncing data into your application. CoreProc Nova Data Sync provides Nova tooling to import and update Eloquent records from external data sources, helping keep your admin data current with repeatable sync operations.
At a glance
Frequently asked questions about Nova Data Sync
- What is CoreProc Nova Data Sync used for in Laravel Nova?
- CoreProc Nova Data Sync is a Laravel Nova package for importing and updating Eloquent records from external data sources through Nova admin tooling. It is intended for repeatable sync and bulk import operations so back-office data stays current. It fits best in Nova-based admin stacks, especially where bulk imports must handle multi-tenant database connections carefully.
- How do I install coreproc/nova-data-sync with Composer?
- Install it as a normal Composer dependency and pin the version you have validated, such as 3.0.2. Update the lockfile and review the package diff before deploying. Because 3.0.2 is described as a patch-level release, confirm whether any configuration or publish steps changed despite the small version bump.
- Do I need to publish configuration or run migrations after installing coreproc/nova-data-sync?
- The provided overview does not list specific publish or migration steps for this package. Treat configuration review as part of your upgrade checklist, especially when moving to 3.0.2. Check the package source and release diff to confirm whether any config, publish, or database setup steps apply to your application.
- Which Laravel, Nova, and PHP versions are supported by coreproc/nova-data-sync?
- The provided context does not include an explicit Laravel, Nova, or PHP support matrix. Verify the package composer.json constraints against your application versions and your tenancy package before adopting it. Run staging tests on the exact Laravel, Nova, PHP, queue, and database stack you plan to use in production.
- Does coreproc/nova-data-sync work with multi-tenant landlord and tenant databases?
- Version 3.0.2 specifically improves BulkImportProcessor connection handling in multi-tenant setups, so landlord and tenant database separation is a relevant use case. Confirm which tenancy package or custom landlord/tenant pattern your application uses and validate connection switching in your own environment. The release notes indicate a patch-level bug fix rather than a guaranteed fix for every tenancy pattern.
- What changed in coreproc/nova-data-sync 3.0.2 for BulkImportProcessor?
- Version 3.0.2 improves BulkImportProcessor connection handling in multi-tenant setups. The change is described as a patch-level bug fix, not a breaking change. Review the 3.0.1-to-3.0.2 diff and add regression coverage for landlord and tenant connection switching before production deployment.
- Can BulkImportProcessor run in queues, CLI, or both?
- The provided assessment flags queue, CLI, and scheduled job behavior as key questions rather than confirmed details. Validate whether imports run in queue workers, command-line jobs, or both in your application. Confirm that queue workers, scheduled jobs, and CLI imports all receive the same connection-handling behavior after upgrading to 3.0.2.
- How should I test coreproc/nova-data-sync for tenant connection leaks?
- Add a regression test that exercises a bulk import while switching between tenant and landlord contexts. Run staging tests with representative tenants, import volumes, queue workers, and connection limits. Monitor for stale connections, failed imports, partial imports, and tenant-context contamination before canarying to production.
- What production risks and failure modes should I monitor with coreproc/nova-data-sync?
- Watch for connection leakage between landlord and tenant contexts, stale connections after jobs, partial imports, queue worker reuse, timeouts on large batches, and tenant-context contamination if the fix regresses. Bulk imports can be long-running and queue-intensive, so validate worker memory, database connection limits, timeouts, and tenant fan-out. Monitor import job failures, database connection counts, and tenancy-context errors during rollout.
- What alternatives exist and what maintenance should I expect for coreproc/nova-data-sync?
- Alternatives include custom Artisan import commands, general-purpose ETL tooling, or other Nova import packages, depending on whether you need Nova admin tooling and multi-tenant connection handling. Expected maintenance for this patch is low, but the multi-tenant connection logic should remain covered by automated regression tests. Track upstream releases and confirm maintainer responsiveness because this area is sensitive to tenancy and queue changes.
Weaver
How can I help you explore Laravel packages today?