Queue e-mails for background processing #124

Nieuw probleem

aheathershaw · 2019-07-13T18:23:31+01:00

aheathershaw reageerde

2019-07-13 18:23:31 +01:00

Eigenaar

Queue e-mails in the database and use a Laravel queue worker to actually send the e-mails on a background job.

aheathershaw heeft dit 2019-07-13 18:23:31 +01:00 aan de mijlpaal Version 2.2.0-beta.1 toegevoegd

aheathershaw heeft dit 2019-07-13 18:23:31 +01:00 aan zichzelf toegewezen

aheathershaw voegde het

bug

label 2019-07-13 18:23:31 +01:00 toe

aheathershaw titel aangepast van ~~Update forgot password form to BS4~~ naar Queue e-mails for background processing

2019-07-13 21:06:56 +01:00

aheathershaw voegde het

wip

label 2019-07-13 21:07:28 +01:00 toe

aheathershaw verwees naar dit probleem vanuit commit 2019-07-13 21:40:18 +01:00'

#124, #125, #126: Started implementing e-mail queueing. Fixed the display of validation messages on the forgotten password form. Corrected the generation of the action URL when the APP_URL environment settings is not configured.

aheathershaw reageerde

2019-07-13 22:18:51 +01:00

Eigenaar

The 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.

The 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.

aheathershaw reageerde

2019-07-13 22:30:08 +01:00

Eigenaar

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

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

aheathershaw verwees naar dit probleem vanuit commit 2019-07-14 12:29:32 +01:00'

#124: E-mails now send and log to the database as sent when queuing is not enabled

aheathershaw verwees naar dit probleem vanuit commit 2019-07-14 14:18:18 +01:00'

#124: Updated the user self-registration required and user self-activated e-mails to be notifications so they can be queued.

aheathershaw verwees naar dit probleem vanuit commit 2019-07-14 14:35:30 +01:00'

#124: Updated the change e-mail confirmation to be a notification

aheathershaw verwees naar dit probleem vanuit commit 2019-07-14 15:58:16 +01:00'

#124: Converted the comment-related e-mails to be queueable

aheathershaw verwees naar dit probleem vanuit commit 2019-07-14 16:13:00 +01:00'

#124: Made the queue settings configurable through the .env file

aheathershaw verwijderde het

wip

label 2019-07-14 16:15:03 +01:00

aheathershaw heeft dit probleem gesloten

2019-07-14 16:15:07 +01:00

aheathershaw reageerde

2019-07-14 16:16:09 +01:00

Eigenaar

This is now complete. To run the queue, use the command below:

php artisan bt-queue:send-emails

or reference the example systemd service in resources/systemd/blue-twilight-email.service.

This is now complete. To run the queue, use the command below: `php artisan bt-queue:send-emails` or reference the example systemd service in `resources/systemd/blue-twilight-email.service`.

aheathershaw verwees naar dit probleem vanuit commit 2019-07-14 16:16:38 +01:00'

#124: Corrected the base class in the comment replied to mailable.

aheathershaw voegde de

enhancement

toe en verwijderde de

bug

labels 2019-09-07 11:07:55 +01:00

Log in om deel te nemen aan deze discussie.