Gunicorn as WSGI server in Django - Mini Project: Build & Apply

Gunicorn as WSGI server

📖 Scenario: You have a simple Django project and want to serve it using Gunicorn, a WSGI server. This setup helps your Django app handle web requests efficiently in a production-like environment.

🎯 Goal: Set up Gunicorn to serve your Django project by creating the necessary configuration and running the server with the correct command.

📋 What You'll Learn

Create a basic Django project named myproject

Add a Gunicorn configuration variable for the number of workers

Write the command to run Gunicorn with the WSGI application

Complete the setup by specifying the bind address for Gunicorn

💡 Why This Matters

🌍 Real World

Gunicorn is a popular WSGI server used to serve Django applications in production environments, making your app ready for real users.

💼 Career

Knowing how to configure and run Gunicorn with Django is essential for backend developers and DevOps engineers working with Python web apps.

1

Create a Django project named myproject

Create a Django project by running the command django-admin startproject myproject. Then, create a file named gunicorn_config.py inside the myproject directory with a variable workers set to 3.

Django

# Create the file gunicorn_config.py inside myproject and set workers = 3
# Your code here

Hint

Inside the myproject folder, create gunicorn_config.py and write workers = 3.

2

Add a Gunicorn configuration variable for the bind address

In the gunicorn_config.py file inside myproject, add a variable called bind and set it to "127.0.0.1:8000" to specify the address Gunicorn will listen on.

Django

workers = 3
# Add bind variable with value "127.0.0.1:8000"
# Your code here

Hint

Set bind = "127.0.0.1:8000" in gunicorn_config.py to tell Gunicorn where to listen.

3

Write the command to run Gunicorn with the WSGI application

Write the command to run Gunicorn serving the Django project myproject using the WSGI application myproject.wsgi:application. Use the configuration file myproject/gunicorn_config.py by adding --config myproject/gunicorn_config.py to the command.

Django

workers = 3
bind = "127.0.0.1:8000"
# Write the gunicorn run command below
# Your code here

Hint

Use gunicorn myproject.wsgi:application --config myproject/gunicorn_config.py to start the server.

4

Complete the setup by specifying the bind address for Gunicorn

Ensure the bind variable in gunicorn_config.py is set to "127.0.0.1:8000" so Gunicorn listens on localhost port 8000. This completes the basic Gunicorn setup for your Django project.

Django

workers = 3
bind = "127.0.0.1:8000"
# Confirm bind address is set correctly
# Your code here

Hint

Double-check that bind is set to "127.0.0.1:8000" in gunicorn_config.py.

Practice

1. What is the primary role of Gunicorn when used with a Django project?

easy

A. It replaces the Django ORM for database queries.

B. It acts as a bridge between the web server and the Django application.

C. It manages static files like CSS and JavaScript.

D. It compiles Django templates into HTML.

Solution

1. Step 1: Understand Gunicorn's purpose

   Gunicorn is a WSGI server that connects web requests to the Django app code.

2. Step 2: Identify what Gunicorn does not do

   Gunicorn does not handle database queries, static files, or template compilation directly.

3. Final Answer:

   It acts as a bridge between the web server and the Django application. -> Option B

4. Quick Check:

   Gunicorn = bridge server [OK]

Hint: Gunicorn connects web requests to Django code [OK]

Common Mistakes:

• Thinking Gunicorn manages static files
• Confusing Gunicorn with Django ORM
• Assuming Gunicorn compiles templates

2. Which of the following is the correct command to start Gunicorn for a Django project named myproject with the default WSGI application?

easy

A. gunicorn myproject.settings:application

B. gunicorn myproject.manage:application

C. gunicorn myproject.urls:application

D. gunicorn myproject.wsgi:application

Solution

1. Step 1: Identify the WSGI application path

   In Django, the WSGI app is located at projectname.wsgi:application.

2. Step 2: Match the correct command format

   The correct Gunicorn command uses gunicorn myproject.wsgi:application.

3. Final Answer:

   gunicorn myproject.wsgi:application -> Option D

4. Quick Check:

   WSGI app path = myproject.wsgi:application [OK]

Hint: Gunicorn command uses <project>.wsgi:application [OK]

Common Mistakes:

• Using manage or settings instead of wsgi
• Confusing URLs module with WSGI
• Omitting the ':application' part

3. Given the command gunicorn --workers 3 --bind 0.0.0.0:8000 myproject.wsgi:application, what will happen when you run it?

medium

A. Gunicorn will start 1 worker and listen only on localhost at port 8000.

B. Gunicorn will fail because the bind address is invalid.

C. Gunicorn will start 3 worker processes and listen on all network interfaces at port 8000.

D. Gunicorn will start 3 workers but will not bind to any port.

Solution

1. Step 1: Analyze the --workers option

   The command specifies 3 workers, so Gunicorn will start 3 worker processes.

2. Step 2: Analyze the --bind option

   Binding to 0.0.0.0:8000 means listening on all network interfaces at port 8000.

3. Final Answer:

   Gunicorn will start 3 worker processes and listen on all network interfaces at port 8000. -> Option C

4. Quick Check:

   --workers 3 + --bind 0.0.0.0:8000 = Gunicorn will start 3 worker processes and listen on all network interfaces at port 8000. [OK]

Hint: 0.0.0.0 binds all interfaces, workers set process count [OK]

Common Mistakes:

• Assuming 0.0.0.0 is invalid
• Thinking workers default to 1 always
• Ignoring the bind port

4. You run gunicorn myproject.wsgi:application --workers two and get an error. What is the likely cause?

medium

A. The workers option must be a number, not a word.

B. The WSGI application path is incorrect.

C. Gunicorn does not accept the --workers option.

D. The command is missing the --bind option.

Solution

1. Step 1: Check the --workers option value

   The value 'two' is a word, but --workers expects an integer number.

2. Step 2: Confirm Gunicorn option requirements

   Gunicorn requires a numeric value for workers; using a word causes an error.

3. Final Answer:

   The workers option must be a number, not a word. -> Option A

4. Quick Check:

   --workers needs number, not text [OK]

Hint: Workers count must be numeric, not text [OK]

Common Mistakes:

• Assuming WSGI path error causes this
• Thinking --workers is unsupported
• Believing --bind is mandatory for this error

5. You want to deploy your Django app with Gunicorn on a server accessible only on port 8080 and use 4 workers for better performance. Which command correctly achieves this?

hard

A. gunicorn --workers 4 --bind 0.0.0.0:8080 myproject.wsgi:application

B. gunicorn --workers 4 --bind 127.0.0.1:8080 myproject.wsgi:application

C. gunicorn --workers 1 --bind 0.0.0.0:8080 myproject.wsgi:application

D. gunicorn --bind 0.0.0.0:80 myproject.wsgi:application

Solution

1. Step 1: Set the correct number of workers

   The requirement is 4 workers, so use --workers 4.

2. Step 2: Bind to port 8080 on all interfaces

   Binding to 0.0.0.0:8080 makes the app accessible on port 8080 from any network interface.

3. Step 3: Verify the WSGI application path

   The path myproject.wsgi:application is the correct WSGI app for Django.

4. Final Answer:

   gunicorn --workers 4 --bind 0.0.0.0:8080 myproject.wsgi:application -> Option A

5. Quick Check:

   4 workers + bind 0.0.0.0:8080 = gunicorn --workers 4 --bind 0.0.0.0:8080 myproject.wsgi:application [OK]

Hint: Use --workers 4 and bind 0.0.0.0:8080 for access [OK]

Common Mistakes:

• Binding only to localhost (127.0.0.1) limits access
• Using wrong port number
• Setting wrong number of workers