Gunicorn as WSGI server in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run Gunicorn serving a Django project named myproject.

Django

gunicorn [1].wsgi

Drag options to blanks, or click blank then click option'

Amyproject

Bmanage

Csettings

Dapps

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'manage' instead of the project name.

Trying to run Gunicorn without specifying the WSGI module.

Gunicorn runs the WSGI application by pointing to the Django project's wsgi module, which is myproject.wsgi.

2fill in blank

medium

Complete the command to bind Gunicorn to listen on port 8000.

Django

gunicorn myproject.wsgi --bind [1]

Drag options to blanks, or click blank then click option'

A0.0.0.0:8000

Blocalhost:80

C127.0.0.1:22

D0.0.0.0:443

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 80 or 443 which require root privileges.

Binding only to localhost which restricts external access.

Binding to 0.0.0.0:8000 makes Gunicorn listen on all network interfaces at port 8000.

3fill in blank

hard

Fix the error in the Gunicorn command to run with 4 worker processes.

Django

gunicorn myproject.wsgi --workers=[1]

Drag options to blanks, or click blank then click option'

A-4

Btwo

Czero

D4

Attempts:

3 left

💡 Hint

Common Mistakes

Using words like 'two' or 'zero' instead of numbers.

Using negative numbers for workers.

The number of workers must be a positive integer without quotes or signs, so 4 is correct.

4fill in blank

hard

Fill both blanks to run Gunicorn with 3 workers and bind to localhost port 9000.

Django

gunicorn myproject.wsgi --workers=[1] --bind [2]

Drag options to blanks, or click blank then click option'

A3

B0.0.0.0:8000

C127.0.0.1:9000

D4

Attempts:

3 left

💡 Hint

Common Mistakes

Using 4 workers instead of 3.

Binding to 0.0.0.0 instead of localhost.

3 workers is a valid number, and binding to 127.0.0.1:9000 listens on localhost port 9000.

5fill in blank

hard

Fill all three blanks to run Gunicorn with 2 workers, bind to all interfaces on port 8080, and enable access log.

Django

gunicorn [1].wsgi --workers=[2] --bind [3] --access-logfile -

Drag options to blanks, or click blank then click option'

Amyproject

B2

C0.0.0.0:8080

Dmanage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'manage' instead of the project name.

Binding to wrong IP or port.

Forgetting to specify workers.

The project name is myproject, workers set to 2, and binding to 0.0.0.0:8080 listens on all interfaces at port 8080. The --access-logfile - option enables access logs to the console.

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