Gunicorn as WSGI server in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Gunicorn in the context of Django?

Gunicorn is a WSGI server that runs Django applications by handling HTTP requests and forwarding them to Django for processing.

beginner

Why do we use Gunicorn instead of Django's built-in server in production?

Django's built-in server is for development only. Gunicorn is more efficient, handles multiple requests concurrently, and is designed for production use.

beginner

How do you start a Django app with Gunicorn?

Run the command: gunicorn myproject.wsgi:application where myproject.wsgi:application points to the WSGI application callable.

beginner

What does WSGI stand for and why is it important?

WSGI means Web Server Gateway Interface. It is a standard that allows web servers like Gunicorn to communicate with Python web apps like Django.

intermediate

Name one key feature of Gunicorn that helps with handling multiple users.

Gunicorn uses worker processes to handle many requests at the same time, improving performance and reliability.

What role does Gunicorn play in a Django application?

A It serves as a WSGI server to handle HTTP requests.

B It is a database management system.

C It is a front-end framework.

D It is a CSS styling tool.

Gunicorn acts as a WSGI server that manages HTTP requests and forwards them to Django.

Which command starts a Django app using Gunicorn?

A python manage.py startapp

B django-admin runserver

C npm start

D gunicorn myproject.wsgi:application

The command 'gunicorn myproject.wsgi:application' starts the Django app with Gunicorn as the WSGI server.

Why is Django's built-in server not recommended for production?

A It is too slow and not designed for multiple users.

B It does not support Python.

C It only works on Windows.

D It requires a database connection.

Django's built-in server is for development and cannot efficiently handle multiple users or heavy traffic.

What does WSGI enable between Gunicorn and Django?

A Database queries.

B A standard interface for communication.

C CSS styling.

D JavaScript execution.

WSGI provides a standard way for web servers like Gunicorn to communicate with Python web apps like Django.

How does Gunicorn improve handling many users at once?

A By storing data in cookies.

B By caching CSS files.

C By using multiple worker processes.

D By running JavaScript faster.

Gunicorn uses worker processes to handle multiple requests concurrently, improving performance.

Explain what Gunicorn does when running a Django application.

Think about how web servers and Django work together.

Describe why WSGI is important for Python web applications like Django.

Consider how different parts of a web app talk to each other.

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