Queue e-mails for background processing #124
Labels
Sans jalon
Sans assignation
1 participants
Notifications
Échéance
Aucune échéance n'a été définie.
Dépendances
Aucune dépendance définie.
Référence : aheathershaw/blue-twilight#124
Chargement…
Référencer dans un nouveau ticket
Sans contenu.
Supprimer la branche "%!s(<nil>)"
La suppression d’une branche est permanente. Bien qu’une branche supprimée puisse temporairement subsister, elle NE PEUT PAS être facilement restaurée. Continuer ?
Queue e-mails in the database and use a Laravel queue worker to actually send the e-mails on a background job.
Update forgot password form to BS4par Queue e-mails for background processingThe best way I can see this working is to use Laravel Notifications and dynamically adjust the “via” result.
(Laravel can not choose whether to queue a notification dynamically.)
We could have a custom notification channel that writes it to the database and a custom worker that processes that table.
This would however mean converting all Mailables to Notifications.
Actually as of 5.3.7, you can use Mailables in conjunction with notifications:
https://laracasts.com/discuss/channels/laravel/laravel-53-using-mailable-inside-a-notification?page=0
This is now complete. To run the queue, use the command below:
php artisan bt-queue:send-emailsor reference the example systemd service in
resources/systemd/blue-twilight-email.service.