Is the NGINX block for 500.html necessary?

[YPCrumble]

Currently we include the following block for a few 500-level errors:

    error_page 500 502 504 /500.html;
    location = /500.html {
        root {{ project_path }}/{{ application_name }}/templates/;
    }

However, this seems project-specific. My suggestion is to remove this block and allow users to manage 500-level errors that aren't 503 (Service Unavailable, related to the maintenance page) themselves.

[jcalazan]

@YPCrumble It's been a while since I've looked into these but I believe this used to be the standard location to place custom 5xx templates in Django.

I think some projects do use a different structure where the templates folder is inside each app folder so you might be right and it's better to just remove it and let the user customize it. I think Django will simply render the generic 5xx page if there's no template found, so not a big deal to remove it.

[jcalazan]

Actually thinking about it again, most new projects probably don't even have a custom 500.html template, so I think removing it is a good call. 👍