--snip-}--snip-this change tells django to look in the root template directory for the error page templates viewing the error pages locally if you want to see what the error pages look like on your system before pushing them to herokuyou'll first need to set debug=false on your local settings to suppress the default django debug pages to do somake the following changes to settings py (make sure you're working in the part of settings py that applies to the local environmentnot the part that applies to heroku)settings py --snip-security warningdon' run with debug turned on in productiondebug false allowed_hosts ['localhost'--snip-you must have at least one host specified in allowed_hosts when debug is set to false now request topic or entry that doesn' belong to you to see the error pageand request url that doesn' exist (such as localhost: /letmein/to see the error page when you're finished checking the error pagesset debug back to true to further develop learning log (make sure debug is still set to false in the section of settings py that applies to the heroku deployment note the error page won' show any information about the user who' logged inbecause django doesn' send any context information in the response when there' server error pushing the changes to heroku now we need to commit the template changes and push them live to herokuu (ll_env)learning_loggit add (ll_env)learning_loggit commit -am "added custom and error pages files changed insertions(+) deletions(-create mode learning_log/templates/ html create mode learning_log/templates/ html (ll_env)learning_loggit push heroku master --snip-remoteverifying deploy done styling and deploying an app