Weave Code
Reminder Notifications Laravel Package
componist/reminder-notifications
Laravel package for queued email reminder notifications with a Livewire v4 dashboard. Supports daily (HH:MM), monthly (day 1–30), and yearly (day/month) schedules, with migrations, routes, views, and configurable Livewire components.
Livewire-powered reminder notifications for Laravel.
Frequently asked questions about Reminder Notifications
- How do I install this package in a Laravel 12 project?
- Run `composer require componist/reminder-notifications`, then execute `composer dump-autoload` and `php artisan migrate`. Ensure Livewire v4 and a queue worker are already configured. The package auto-registers migrations, routes, and Livewire components via its service provider.
- Will this work with Laravel 11 or older?
- No, the package explicitly requires Laravel 12. Downgrading may break dependencies like Livewire v4 or Laravel’s queue system. Test thoroughly if considering a fork or alternative like `spatie/scheduled-reminders`.
- Can I customize the email templates without modifying the package?
- Yes, override the package’s Blade views by publishing them with `php artisan vendor:publish --tag=remindernotifications-views`. Place custom templates in `resources/views/vendor/remindernotifications/` and extend the base templates.
- How does the Livewire dashboard handle timezone for daily reminders?
- The dashboard uses Laravel’s default timezone (config/app.php). Daily reminders (HH:MM) respect this setting, including Daylight Saving Time adjustments. Ensure your app’s timezone matches user expectations to avoid misfired reminders.
- What happens if I have 10,000+ reminders to send daily?
- The package dispatches reminders as queued jobs, but scaling depends on your queue driver (e.g., Redis or database). Monitor job failures and consider batching recipients manually. The package lacks built-in segmentation or bulk-processing optimizations.
- Do I need to run a queue worker for this to function?
- Yes, the package relies on Laravel’s queue system to delay and process reminders. Configure a queue driver (e.g., `redis`, `database`) and start workers with `php artisan queue:work`. Failed jobs require supervision (e.g., Laravel Horizon or Supervisor).
- Are there alternatives if I don’t use Livewire?
- Yes, consider `spatie/scheduled-reminders` (no Livewire) or `laravel-notifications` for more flexible notification systems. This package’s Livewire dashboard is optional—you could build a custom API endpoint or use the core reminder logic without the frontend.
- How do I test monthly reminders for February 30th?
- The package validates days (1–30) but doesn’t handle edge cases like February 30th. Override the validation logic in `app/Providers/AppServiceProvider` or extend the `Reminder` model to use Carbon’s `isValid()` method for safer date handling.
- Can I integrate this with a custom mail driver (e.g., AWS SES VPC)?
- Yes, the package uses Laravel’s mail facade, so any configured mail driver will work. Test with your custom driver first, as some (e.g., SES with VPC endpoints) may require additional configuration like TLS settings or regional endpoints.
- What if my app already has a `reminders` table? Will migrations conflict?
- The package creates a `reminder_notifications` table. If your existing table has similar fields (e.g., `title`, `email`), you may need to merge data manually. Use `php artisan migrate:status` to check for conflicts and adjust the package’s migrations if needed.
Weaver
How can I help you explore Laravel packages today?