- Can I install flodaq/ticket-notification-bundle in a Laravel application?
- It is a Symfony bundle built for the Hackzilla Ticketing Symfony bundle, not a Laravel package. It has no Laravel service provider, facade, config publishing, or Composer extra.laravel entry, so it cannot be installed and used as-is in Laravel. Treat it as a design reference and port the notification logic instead.
- Is flodaq/ticket-notification-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle that registers in a Symfony Kernel and depends on Symfony DependencyInjection and EventDispatcher. Its job is to listen for Hackzilla ticketing create or modify events and send emails. The Laravel/PHP framing is misleading because there is no Laravel-shaped surface.
- How do I install flodaq/ticket-notification-bundle?
- In a Symfony app you would require it via Composer and enable it in the Kernel alongside Hackzilla Ticketing. There is no Laravel installation path and no published config to copy. For Laravel you must reimplement the notification behavior rather than install the bundle.
- What Laravel versions does this ticket notification bundle support?
- None. It targets Symfony and Hackzilla Ticketing, so Laravel 8, 9, 10, and 11 are not supported. There is no service provider or package manifest for Laravel. Compatibility with any Laravel version would require a rewrite.
- How does the bundle decide who receives ticket notification emails?
- Recipient resolution is the most valuable part of the repo, likely covering assignee, reporter, watchers, and group or queue owner. The exact rules live in the bundle's event subscribers and configuration. Port these rules carefully into Laravel listeners or notifications.
- Does flodaq/ticket-notification-bundle queue emails or send them synchronously?
- The bundle wires emails through Symfony's mailer, and synchronous sends on ticket creation are a scaling and failure concern. In a Laravel port, replace this with Mailables and Notifications using Mail::queue() or ShouldQueue. That gives retries and keeps ticket requests fast.
- How do I configure ticket notification templates and subjects?
- Templates are likely Twig files rendering ticket summary, link, and change diffs, with Symfony configuration for subjects. There is no Laravel config publishing, so you cannot override views the Laravel way. In a port, convert Twig to Blade and move settings into config/ticketing.php.
- Is flodaq/ticket-notification-bundle actively maintained and safe for production?
- Project maturity is a high risk: about one star, zero dependents, and a single-maintainer org named flodaq, suggesting an internal utility published publicly. There is no CVE history or security policy, though MIT licensing is permissive. Do not rely on it in production without auditing the code.
- What are the alternatives to this bundle for Laravel ticket notifications?
- Look for actively maintained Laravel ticketing or helpdesk packages, or build notifications on Laravel's native Event, Listener, Mailable, and Notification classes. If you already run Hackzilla on Symfony, this bundle fits there. For Laravel, a small custom implementation is usually lower risk than porting a dormant bundle.
- How hard is it to port this bundle's logic to Laravel?
- If the notification logic is roughly 200 to 400 lines, porting is a one-to-two sprint task. Symfony event subscribers map cleanly to Laravel listeners, and Mailables plus queueing replace the mailer wiring. The real blocker is Hackzilla Ticketing itself, which is Doctrine-based and has no Laravel equivalent.