Home/ Questions/Q 6647407
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T00:32:02+00:00

Concerning the built in debugging server started with the manage.py runserver command, the Django

  • 0

Concerning the built in debugging server started with the manage.py runserver command, the Django docs state, “DON’T use this server in anything resembling a production environment.”

If I wanted to develop a Django application over ssh on a remote machine, would using Nginx as a proxy to a running Django debug server be a reasonable thing to do? Is the Django debug server insecure, or just not built to handle large amounts of traffic?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From the Django docs:

    DO NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through security audits or performance tests. (And that’s how it’s gonna stay. We’re in the business of making Web frameworks, not Web servers, so improving this server to be able to handle a production environment is outside the scope of Django.)

    So, that answers the latter two questions. As for the former, it depends on how your debug server is set up. If your server is exposed to the public Internet, doesn’t have a firewall blocking port 8000, and you intend to use runserver with something other than the default 127.0.0.1 address, set up a more ‘proper’ application stack.

    If you’re going to use nginx, why not just use the suggested FastCGI configuration so that your debug environment will be more similar to the future production environment?

    • 0