
Sign up to save your podcasts
Or
Most teams have encountered this basic scenario:
Your application sends out a periodic report to a specific person in the company. Then, at some later point, either another team member wants to start receiving a copy of the report, or you need to remove the original recipient and add a new one.
With a standard Laravel app, you're probably going to need to make this change by deploying a change—either to the environment, or a config file, or the Mailable class itself.
In today's episode we dig into ways we could make it possible for non-technical users to manage outgoing email messages: from the recipient(s), to the message content, to even the logic that determines when and if a message is sent.
5
88 ratings
Most teams have encountered this basic scenario:
Your application sends out a periodic report to a specific person in the company. Then, at some later point, either another team member wants to start receiving a copy of the report, or you need to remove the original recipient and add a new one.
With a standard Laravel app, you're probably going to need to make this change by deploying a change—either to the environment, or a config file, or the Mailable class itself.
In today's episode we dig into ways we could make it possible for non-technical users to manage outgoing email messages: from the recipient(s), to the message content, to even the logic that determines when and if a message is sent.
283 Listeners
58 Listeners
627 Listeners
30,045 Listeners
55 Listeners
24 Listeners
983 Listeners
6,892 Listeners
17 Listeners
11 Listeners
8 Listeners
15 Listeners
2 Listeners
7 Listeners