How to Deploy Django with Nginx and uWSGI: A Step‑by‑Step Guide

Running a Django app locally is easy with the built‑in runserver, but production deployment requires handling static files, security, and efficiency.

Fixing missing static files

When Debug is off and Nginx is not yet configured, you can serve static assets directly by running:

python manage.py runserver 0.0.0.0:8000 --insecure

Collect static files

Before handing over to Nginx, gather all static resources into the static directory:

python manage.py collectstatic

Restarting uWSGI

Create a restart.sh script in the same directory as manage.py with the following commands to reload uWSGI after code changes:

killall uwsgi

uwsgi -x django_socket.xml

Replace django_socket.xml with the actual configuration file name.

Additional project tweaks

Add DOMAIN = '127.0.0.1' (or your actual IP/domain) to settings.py.

Update the base.html template to reference static assets, e.g., change the favicon link to /static/favicon.ico.

In the URL configurations of accounts and people apps, prefix view imports with apps. (e.g., apps.accounts.views).

Consider securing the admin interface by changing its URL or restricting IP ranges.