-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add failover transport to MailSetting #1315
base: develop
Are you sure you want to change the base?
Conversation
mjauvin
commented
Feb 23, 2025
•
edited
Loading
edited
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add this validation rule:
'failover_mailers' => 'required_if:send_mode,'.self::MODE_FAILOVER
Co-authored-by: Matteo Trubini <7964032+matteotrubini@users.noreply.github.com>
Co-authored-by: Matteo Trubini <7964032+matteotrubini@users.noreply.github.com>
Co-authored-by: Matteo Trubini <7964032+matteotrubini@users.noreply.github.com>
Co-authored-by: Matteo Trubini <7964032+matteotrubini@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@mjauvin are people able to configure the transports through the backend as well as use the failover transport? |
No, they would need to configure the other mailers in the config |
As I wrote in discord: <@164272636988227584> I'm thinking we should move away from the SettingsModel behavior for the MailSetting model and have an active record instead (for the default mailer). That would allow setting multiple records for the different transports to support the failover (and roundrobin in Laravel 11) |