When developing #Laravel applications I'm always a little afraid of sending emails to actual customers or placing real orders by accident. So I came up with a habit that works super well for me and maybe this will suit you as well.
In my /config/mail.php I add a 'developer' email address and ensure in my AppServiceProvider all emails are sent to this address when in non-production environments no matter what. Makes me build and test stuff way more confidently 😁
@rolfdenhartog That's a great solution, thanks! For such cases I usually work with Laravel Herd. However, many times I know my clients work with outlook for example and then I ensure everything looks fine in outlook. But still, your approach in general feels cleaner than adding my code snippet to the service provider.
I have a FREE book on object-oriented programming available for you to download and enjoy. It's my way of giving back to the #php community. Check it out: https://masteringobjectorientedphp.com
Have you ever stood up, from scratch, a completely new version of your application in a production-ready state?
If you haven't, you should.
You may never need to fully stand up a complete production instance, but what happens if a part goes down like your database, your webservers, or your jobs? Are you prepared for emergencies?
@sarah I had to do this some time last year. Proud to say: it only took us a few hours, in part because we had copious backups and had trained for this. 👍
@sarah We do that, several times a year, one where we restore crashed servers, one where we restore single installations, one where we restore multiple, one for hot backup, one for cold backups.
Everytime we review the procedures, and fix any changes we encounter.