Understanding the Difference Between manage.py and settings.py in Django (CS50 Web)

[Rajeev Bagra]

When starting with Django in the CS50 Web course, two files appear in almost every project:

• manage.py
• settings.py

 

Both are essential, but they serve completely different purposes. Understanding their roles makes it much easier to understand how a Django project starts and operates.

---

The Big Idea

File	Purpose
manage.py	The command-line utility used to run Django commands.
settings.py	The configuration file that tells Django how the project should behave.

A simple analogy:

manage.py = Driver
settings.py = Map and instructions
Django = Car

The driver tells the car what to do, while the map and instructions tell the car how to operate.

---

What Is manage.py?

manage.py is Django’s command center. It allows us to execute administrative commands from the terminal.

A typical manage.py file looks like this:

#!/usr/bin/env python

import os
import sys

def main():
    os.environ.setdefault(
        'DJANGO_SETTINGS_MODULE',
        'wiki.settings'
    )

    from django.core.management import execute_from_command_line

    execute_from_command_line(sys.argv)

if __name__ == '__main__':
    main()

The key line is:

os.environ.setdefault(
    'DJANGO_SETTINGS_MODULE',
    'wiki.settings'
)

This tells Django:

Use the settings stored in wiki/settings.py.

---

What Commands Does manage.py Run?

Some common examples:

Start the development server:

python manage.py runserver

Create migrations:

python manage.py makemigrations

Apply migrations:

python manage.py migrate

Create an administrator account:

python manage.py createsuperuser

Open the Django shell:

python manage.py shell

Notice that manage.py does not store configuration settings. Its job is simply to execute commands.

---

What Is settings.py?

settings.py is the project’s configuration file. It contains all the information Django needs in order to run properly.

---

Installed Applications

INSTALLED_APPS = [
    'encyclopedia',
    'django.contrib.admin',
    'django.contrib.auth',
    ...
]

This tells Django which applications belong to the project.

---

Database Configuration

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
    }
}

This tells Django which database system to use and where the database file is located.

---

Debug Mode

DEBUG = True

This enables detailed error messages during development.

---

Template Configuration

TEMPLATES = [...]

This tells Django where to look for HTML templates.

---

Static Files

STATIC_URL = '/static/'

This tells Django how CSS, JavaScript, and image files should be served.

---

How Do They Work Together?

Suppose we run:

python manage.py runserver

The sequence is:

manage.py
    ↓
Loads wiki.settings
    ↓
Reads INSTALLED_APPS
Reads DATABASES
Reads TEMPLATES
Reads STATIC_URL
    ↓
Starts Django Server

In other words:

1. manage.py receives the command.
2. It tells Django which settings file to use.
3. Django loads settings.py.
4. Django reads all project configurations.
5. The requested command is executed.

---

CS50 Wiki Project Example

In the CS50 Wiki project, when you run:

python manage.py runserver

Django loads:

INSTALLED_APPS = [
    'encyclopedia'
]

and knows that the Encyclopedia application exists.

It then reads:

DATABASES

to connect to the SQLite database.

Next, it reads:

ROOT_URLCONF = 'wiki.urls'

to locate the URL routes.

Only after all of these settings are loaded can the server start successfully.

---

Common Beginner Mistake

Many beginners think that manage.py contains the project settings because it references:

'wiki.settings'

However, manage.py only points Django to the settings file. The actual configuration is stored inside settings.py.

---

Key Takeaways

• manage.py is used to run Django commands.
• settings.py stores project configuration.
• manage.py loads settings.py before executing commands.
• Without settings.py, Django would not know how the project is configured.
• Without manage.py, running Django commands would be much more difficult.

---

Final Summary

manage.py answers the question:

“What should Django do?”

settings.py answers the question:

“How should Django be configured?”

Understanding this relationship is one of the first major steps toward understanding how a Django application starts, loads its configuration, and serves web pages.

[Author]

Posts