Incoming VS Maily

This article from HoneyBadger explains most relevant topics about Rails DB transactions.

Honeybadger is a powerful error-monitoring tool for Python applications. Integrating an error monitoring service like Honeybadger into your development workflow provides numerous benefits for effectively managing exceptions. From real-time notifications and error grouping to rich diagnostics and trend analysis, Honeybadger equips you with the tools you need to quickly identify, investigate, and resolve errors and ultimately enhance the overall quality and reliability of your applications. To demo this, let's now explore some features and examples of integrating Honeybadger into your Python code.

honeybadger.io - Exception, uptime, and cron monitoring. Free for small teams and open-source projects (12,000 errors/month).

It sounds like you want to implement an exception monitoring tool like Honeybadger (my company), Sentry, or similar. They will tell you when someone encounters an error with your app, where the error occurred, and what the state of the app was (parameters, etc.) at the time of the error.

You may wonder why this is a problem. In the case of this code, we're sending the user's username to a third-party service. While username isn't inherently sensitive data, it certainly has to potential to be and should be treated as such. It's better to use IDs that can't identify the user if the third party—in this case, honeybadger—is breached. You can see the full list of supported data types, sorted by category, on the docs.

Sign up on the Honeybadger website and click on ‘start free trial’, as shown in the following image.

I don't have a reply for you but recently, a user here posted this gem and maybe it'll let you manage your email templates in-app: https://github.com/markets/maily

- Rubygems: https://rubygems.org/gems/maily/versions/2.0.0 - Changelog: https://github.com/markets/maily/blob/master/CHANGELOG.md - Source code: https://github.com/markets/maily