django-admin startproject Explained

Django can generate a working project skeleton for you. The startproject command builds the folders and files you need to begin. 🏗️

You now have an outer mysite folder holding manage.py plus an inner config package. That structure is the backbone of every Django app.

The manage.py file is your command center. You run servers, migrations, and admin tasks through it for the rest of the project.

Inside sits a package named after your project. This config package holds the settings that wire everything together.

The settings.py file controls your whole project: installed apps, the database, templates, and more, all in one Python module.

The urls.py file maps incoming web addresses to your code. It is the front door that decides which view answers each request.

The wsgi.py file is the entry point production servers use to talk to your app over the classic synchronous interface.

The asgi.py file is the modern async entry point. It supports websockets and long-lived connections beyond plain HTTP.

An __init__.py marks the config folder as a Python package, so its modules can be imported across the project.

Add a trailing dot to put config files in the current folder. This dot skips the extra wrapping directory many beginners trip over.

Pick a clear project name, since it becomes a Python package. Avoid names like django or test that clash with existing modules.

Let's check the generated files.

You scaffolded a project and toured its files: manage.py, settings, urls, wsgi, and asgi. The skeleton is ready to grow. 🎉