- Is nti/auto-delete-bundle a Laravel package?
- No. It is a Symfony bundle named NTIAutoDeleteBundle that integrates through Symfony bundle registration and Doctrine metadata, not Laravel's service-provider model. For Laravel, vendor or port the deletion pattern into an Artisan command rather than installing it as a dependency.
- Can I install nti/auto-delete-bundle in a Laravel app?
- Composer may install the package, but the Symfony bundle will not register or run natively in Laravel. You would need an adapter plus Doctrine or a full reimplementation. For Laravel with Eloquent, treat it as an MIT-licensed reference implementation, not an install-and-go dependency.
- How do I install nti/auto-delete-bundle in Symfony?
- Run composer require, enable NTIAutoDeleteBundle in bundles.php, configure your retention rules, and drive the console command from cron or Symfony Scheduler. Check the composer.json constraints for Symfony 6/7 and PHP 8.2+ compatibility before committing. Confirm the bundle's required Doctrine packages are already present in your project.
- Does nti/auto-delete-bundle work with Doctrine ORM?
- It is built for Doctrine ORM and doctrine-bundle, using entity metadata and a console command shape. It is not an Eloquent package and does not understand Laravel models. Verify whether it respects Doctrine lifecycle events, cascades, and foreign-key constraints before production use.
- How do I schedule auto-delete-bundle in Symfony?
- Drive the bundle's console command from cron or Symfony Scheduler with an explicit, monitored schedule. Silent failures are dangerous because expired data can remain past policy without anyone noticing. Add alerting on non-zero exit codes and unexpected deletion counts.
- Does nti/auto-delete-bundle support dry-run or preview mode?
- Dry-run support is not confirmed in the provided context, so treat it as unverified until you inspect the command. A preview mode is essential before running destructive retention in production. If it is missing, wrap or fork the command to log intended deletions without executing them.
- Are deletions hard or soft with nti/auto-delete-bundle?
- The deletion semantics are not documented in the overview, and this distinction matters for compliance and recovery. Inspect the command and repository or service code to confirm whether rows are removed or flagged. Until confirmed, assume hard deletes and test against a disposable database.
- Does nti/auto-delete-bundle batch deletes to avoid N+1 queries?
- Batching, chunking, and transaction safety are unknown from the overview. The implementation could issue a SELECT plus per-row deletes, which risks slow runs and lock escalation on large tables. Review the deletion loop and benchmark it on a production-sized copy before scheduling.
- Is nti/auto-delete-bundle safe for production data deletion?
- High risk applies: it performs irreversible deletions with zero stars, no dependents, and no visible CI or security response process. It is only defensible in a Symfony/Doctrine estate that has a review process capable of auditing a deletion engine. For Laravel, port the algorithm into an internal Artisan command with a dry-run default and audit logging.
- What are alternatives to nti/auto-delete-bundle for Laravel?
- Write an Artisan retention:purge command using chunked Eloquent delete calls, a dry-run default, and structured audit output. You can vendor the MIT-licensed deletion algorithm instead of adding a Symfony dependency and container shim. Evaluate Laravel retention packages carefully, but verify their maintenance, destructive semantics, and test coverage first.