How to Deploy a Django Project Step by Step

Django's runserver command is only intended for local development and testing. It should not be used in production environments.

A production Django deployment typically includes your application code, a WSGI or ASGI server, static file handling, environment variables, and a hosting platform or virtual server. Common tools include Gunicorn, WhiteNoise, PostgreSQL, Render, and PythonAnywhere.

Requirements Before Deployment

Before deploying your Django project, make sure you have:

• A working Django project.
• A requirements.txt file containing all dependencies.
• A GitHub, GitLab, or Bitbucket repository (if required by your hosting provider).
• Production-ready settings including DEBUG=False and proper ALLOWED_HOSTS.
• Environment variables for sensitive information such as database credentials and secret keys.

Step 1: Prepare Your Project for Production

Before deployment, update your Django settings for production. Disable debug mode and configure allowed hosts.

DEBUG = False

ALLOWED_HOSTS = [
    "yourdomain.com",
    "your-app.onrender.com"
]
    

Store sensitive values such as SECRET_KEY and database credentials in environment variables rather than hardcoding them into your project.

Step 2: Install Deployment Packages

Most Django deployments use Gunicorn as the application server, WhiteNoise for serving static files, and PostgreSQL as the database.

Install the required packages:

pip install gunicorn whitenoise psycopg2-binary
    

Update your requirements file:

pip freeze > requirements.txt
    

Step 3: Configure Static Files

Production servers do not automatically serve static files. Configure WhiteNoise and static file settings.

MIDDLEWARE = [
    "django.middleware.security.SecurityMiddleware",
    "whitenoise.middleware.WhiteNoiseMiddleware",
    # Other middleware...
]

STATIC_URL = "/static/"
STATIC_ROOT = BASE_DIR / "staticfiles"
    

Collect static files:

python manage.py collectstatic --noinput
    

Step 4: Run Database Migrations

Apply migrations so the production database matches your Django models.

python manage.py migrate
    

If you are using PostgreSQL, configure your DATABASE_URL environment variable.

Step 5: Choose a Deployment Platform

Popular beginner-friendly deployment platforms include PythonAnywhere and Render.

Example Render build command:

pip install -r requirements.txt && \
python manage.py collectstatic --noinput && \
python manage.py migrate
    

Example start command:

gunicorn your_project_name.wsgi:application
    

Step 6: Start the Django Application

Production deployments use a WSGI or ASGI server instead of Django's development server.

Common Gunicorn command:

gunicorn your_project_name.wsgi:application
    

Example ASGI deployment:

gunicorn your_project_name.asgi:application \
-k uvicorn.workers.UvicornWorker
    

Step 7: Check Deployment Security

Run Django's deployment checklist before going live.

python manage.py check --deploy
    

Also ensure that:

• HTTPS is enabled.
• Secret keys are stored securely.
• Backups are configured.
• Logging and monitoring are enabled.
• Static files are served correctly.

Example Deployment Workflow

1. Build and test your Django project locally.
2. Install Gunicorn, WhiteNoise, and PostgreSQL packages.
3. Create and update requirements.txt.
4. Push your code to GitHub.
5. Set DEBUG=False and configure ALLOWED_HOSTS.
6. Configure environment variables such as SECRET_KEY and DATABASE_URL.
7. Run collectstatic and database migrations.
8. Start the application using Gunicorn or an ASGI server.
9. Run deployment security checks.