Queue e-mails for background processing #124
Etiquetas
Sin Milestone
No asignados
1 participantes
Notificaciones
Fecha de vencimiento
Sin fecha de vencimiento.
Dependencias
No se han establecido dependencias.
Referencia: aheathershaw/blue-twilight#124
Cargando…
Referencia en una nueva incidencia
No se ha proporcionado una descripción.
Eliminar rama "%!s(<nil>) "
Eliminar una rama es permanente. Aunque la rama eliminada puede continuar existiendo durante un corto tiempo antes de que sea eliminada, en la mayoría de los casos NO PUEDE deshacerse. ¿Continuar?
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 BS4a 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.