Sorry, do you mean a command line alternative to
python manage.py runserver ? Loading via
...runserver gives/gave no errors with debugging either enabled or disabled. See original post—with debugging enabled
the site ran fine, without any errors on the console, and without any page faults. When debugging was enabled, the site still loaded without errors on the console, but I got an internal server error on every page access.
My tentative conclusion is that in the default configuation DEBUG = True doesn't debug thoroughly enough. I could have been clearer in my original post, but I still have the same basic concern: DEBUG = True misses some errors that can crash a site, correct? If that's not the case, why did my site fail only after I switched debugging off?
(My primary reason for posting was not to get help fixing the specific error I was dealing with, as frustrating as that error was, but to understand better the limitations of DEBUG = True and how to get general advice for tracking down errors when DEBUG = True fails. I finally saw a reference somewhere else to Django's logging system, which I had somehow missed, and once I had set up Django logging I was able to find my particular problem and fix it. From now on, I'll want to keep the Django log running, unless someone knows of a good reason not to.)