- Is kmj/syncbundle a Laravel package?
- No. kmj/syncbundle is a Symfony2 bundle, registered in AppKernel and wired through Symfony's dependency injection container, not a Laravel package. Laravel has no bundle concept; the equivalent is a service provider with config publishing and package auto-discovery. There is no service provider, no Laravel-facing API, and no framework-agnostic core you could lift into a Laravel application.
- Can I install kmj/syncbundle in a Laravel 10 or 11 app with Composer?
- Native installation will almost certainly fail. The bundle pins symfony/* to ^2.x, which conflicts with the Symfony 6/7 components required by Laravel 10 and 11, so Composer resolution breaks on the first attempt. Confirm this with a short spike rather than assuming, but plan on a blocking conflict.
- What does kmj/syncbundle actually do?
- It is a PHP package for orchestrating data synchronization between an application and external systems. It advertises pluggable sync adapters, configurable field mapping, batch processing with incremental and full runs, and structured logging for auditable sync operations. The stated goal is repeatable, maintainable sync workflows instead of ad-hoc scripts scattered across a codebase.
- Does kmj/syncbundle include a Laravel service provider or auto-discovery?
- There is no Laravel service provider, no config publishing, and no package auto-discovery. Registration happens through Symfony's AppKernel and its dependency injection container. As a result, Laravel's container, facades, and Artisan commands have nothing to bind to out of the box.
- Is kmj/syncbundle actively maintained and safe for production use?
- Treat it as high risk. The repository shows 0 stars, 0 dependents, no visible CI, no tests, and no release history, so there is no maintenance signal. Symfony 2.8 reached end of life in November 2018 and receives no security patches, including for transitive dependencies, and the PHP constraints sit in the 5.3 to 7.x era. Verify the license and last commit date before any spend.
- What is the best alternative to kmj/syncbundle for Laravel data synchronization?
- The recommended path is to reimplement the workflow natively as a Laravel command that dumps, sanitizes, transfers, restores, and invalidates caches. Gate it behind an APP_ENV assertion that refuses to run against production as a target. That is days of work, not months, and it keeps your dependency tree on a supported runtime.
- Can I run kmj/syncbundle in a sidecar container next to a Laravel app?
- Technically yes: run an isolated Symfony2 CLI and invoke it from an Artisan command or a CI job, keeping every Symfony2 dependency out of composer.json. It is strategically weak, though, because you inherit an end-of-life runtime to gain what is most likely a thin wrapper over mysqldump or rsync. Only consider it if a source review shows non-trivial logic such as schema-aware diffing or conflict resolution worth preserving.
- Does kmj/syncbundle anonymize PII when syncing production data to development?
- There is no evidence in the repository of anonymization or PII scrubbing. The stated purpose is production-to-development synchronization, and pulling raw production rows into lower-trust environments is a GDPR and CCPA exposure, not merely a code-quality concern. Treat explicit anonymization as a hard requirement of any replacement you build.
- Does kmj/syncbundle support incremental sync and batch processing?
- The package description advertises batch processing with both incremental and full synchronization runs, along with structured logging for traceable, auditable operations. Those capabilities exist only inside the Symfony2 bundle's own runtime, wired through Symfony's container. To get them in Laravel you would need the sidecar approach or a native reimplementation.
- Is kmj/syncbundle safe for bidirectional production-to-development sync?
- Bidirectional sync fails dangerously here. A direction or configuration error can overwrite production data, and mature tooling gates this behind hard environment assertions that the repository shows no evidence of. Before adopting anything similar, confirm whether sync is one-way or bidirectional, whether dev-to-prod is ever permitted, and what happens on partial failure mid-restore.