Error 500 email #93

New Issue

mpeltriaux · 2022-01-31T09:34:48+01:00

mpeltriaux commented

2022-01-31 09:34:48 +01:00

Status quo

On a DEBUG=False production setting, we do not get any chance to see what happened wrong on the code if any 500 errors occur. At the start of the project, there was the idea to use a custom logger, so the errors could be logged.

However, Django provides a neat feature for sending emails on 500 errors (https://docs.djangoproject.com/en/3.2/howto/error-reporting/)

Enhancement

Activate the mail sending functionality for 500 server errors on the project.

# Status quo On a `DEBUG=False` production setting, we do not get any chance to see what happened wrong on the code if any 500 errors occur. At the start of the project, there was the idea to use a custom logger, so the errors could be logged. However, Django provides a neat feature for sending emails on 500 errors (https://docs.djangoproject.com/en/3.2/howto/error-reporting/) # Enhancement Activate the mail sending functionality for 500 server errors on the project.

mpeltriaux added the

enhancement

label 2022-01-31 09:34:48 +01:00

mpeltriaux self-assigned this 2022-01-31 09:34:48 +01:00

mpeltriaux referenced this issue

2022-01-31 14:52:37 +01:00

Split settings file #95

mpeltriaux added a new dependency 2022-01-31 15:22:04 +01:00

#95 Split settings file

mpeltriaux referenced this issue from a commit

2022-01-31 15:26:02 +01:00

#93 Errors via mail