Weave Code
Notification Bundle Laravel Package
aboutcoders/notification-bundle
Symfony bundle extending SonataNotificationBundle with process control for starting/stopping notification/message processing, ideal for CI environments. Integrates with AbcProcessControlBundle to manage workers and execution flow during builds and tests.
A symfony bundle that adds process control to the SonataNotificationBundle.
Frequently asked questions about Notification Bundle
- Can I use AbcNotificationBundle in a Laravel project?
- No, this bundle is designed for Symfony and relies on SonataNotificationBundle, which isn’t compatible with Laravel. Laravel has native queue systems (e.g., Horizon) that offer similar process control without framework mismatches.
- How does this bundle help with CI/CD pipelines?
- It integrates with AbcProcessControlBundle to programmatically start/stop notification workers, ensuring deterministic queue handling in CI environments. However, Laravel’s `php artisan queue:work --stop` or Horizon’s built-in controls may suffice.
- What Laravel alternatives provide similar process control?
- Laravel’s Horizon (for queues), spatie/laravel-notification-transports (for custom transports), or even Laravel’s native `ShouldQueue` jobs with middleware for retries/throttling. These avoid Symfony dependencies entirely.
- Is SonataNotificationBundle still maintained?
- No, SonataNotificationBundle is abandoned (last commit: 2017). This bundle inherits that risk, making long-term support uncertain. Laravel’s queue ecosystem is actively maintained.
- How do I install this in Symfony?
- Run `composer require aboutcoders/notification-bundle`, register it in `AppKernel.php`, and extend your custom Sonata bundle from `AbcNotificationBundle` instead. Requires AbcProcessControlBundle and SonataNotificationBundle.
- Will this bundle work with Laravel’s queue drivers (Redis, database, etc.)?
- No, it’s tied to Symfony’s process control and Sonata’s architecture. Laravel’s queue drivers integrate natively with Horizon or `queue:work`, offering broader compatibility.
- Can I use this for batch processing notifications?
- Yes, but only in Symfony. For Laravel, consider Laravel’s `batch` package or Horizon’s job batching features, which are optimized for Laravel’s async workflows.
- What’s the upgrade path if SonataNotificationBundle breaks?
- There isn’t one—this bundle depends on it. For Laravel, migrate to spatie/laravel-notification-transports or Horizon, which are actively maintained and framework-native.
- Does this bundle support email/SMS/push notifications?
- It extends SonataNotificationBundle’s transport layer, but Laravel’s `notifications` facade already handles all these types natively with channels like `mail`, `nexmo`, or `slack`.
- How does this compare to Laravel’s `queue:work --stop`?
- This bundle offers programmatic control via AbcProcessControlBundle, while Laravel’s CLI flag (`--stop`) is simpler. For CI/CD, Laravel’s `queue:flush` or Horizon’s `pause` commands may be sufficient.
Weaver
How can I help you explore Laravel packages today?