Description
Right now, all of the emails are sent synchronously. This leads to the user having to wait until the emails are sent to be able to proceed. We should take these and make them asynchronous using Laravel's queues.
NOTE: Queues are implemented in PR #578... Once this is merged this story can move forward.
Acceptance Criteria
Checkbox list of the acceptance criteria for this story
Accepted By: @kjporter
Dev Notes
Queues will already be implemented when this story is started
This story will only involve adding the emails to the queue then the rest should already be handled
This should only involve changing all instances of send() being converted to queue()
Training reminder emails have already been tested. This are a little finicky to test on QA environments, so no more testing of those is required. However, all others should be tested
Testing locally where you can see the log of the emails, instead of them actually sending may be best
Deployment Notes
The environment variable MAIL_FROM_DOMAIN= must be added with the appropriate domain (right now notams.ztlartcc.org)
Description Right now, all of the emails are sent synchronously. This leads to the user having to wait until the emails are sent to be able to proceed. We should take these and make them asynchronous using Laravel's queues.
NOTE: Queues are implemented in PR #578... Once this is merged this story can move forward.
Acceptance Criteria Checkbox list of the acceptance criteria for this story
Accepted By: @kjporter
Dev Notes
send()
being converted toqueue()
XD Notes
Working Branch
async-emails
PR
644
Feature Toggle N/A
QA Notes
Deployment Notes
MAIL_FROM_DOMAIN=
must be added with the appropriate domain (right nownotams.ztlartcc.org
)