Please enable JavaScript.
Coggle requires JavaScript to display documents.
Django Project Structure, How Django Code Work Together - Coggle Diagram
Django Project Structure
Django Project Name Folder
manage.py
The manage.py script is used to create applications, work with databases, and start the development web server.
Note --- run python manage.py to see check all the subcommand.
Note --- run python manage.py help <subcommand> for help on a specific subcommand.
Project Name Folder
urls.py
urls.py defines the site URL-to-view mappings. While this could contain all the URL mapping code, it is more common to delegate some of the mappings to particular applications
setting.py
settings.py contains all the website settings, including registering any applications we create, the location of our static files, database configuration details, etc.
asgi.py
asgi.py is a standard for Python asynchronous web apps and servers to communicate with each other. ASGI is the asynchronous successor to WSGI and provides a standard for both asynchronous and synchronous Python apps (whereas WSGI provided a standard for synchronous apps only). It is backward-compatible with WSGI and supports multiple servers and application frameworks.
__
pycache
__
__
init
__
.py
__
init
__
.py is an empty file that instructs Python to treat this directory as a Python package.
wsgi.py
wsgi.py is used to help your Django application communicate with the webserver. You can treat this as boilerplate.
Application
migration
__
init
__
.py
__
pycache
__
admin.py
apps.py
model.py
test.py
urls.py
views.py
db.sqlite3
dbvjksvirsdhoe
How Django Code Work Together
(
https://media.prod.mdn.mozit.cloud/attachments/2016/09/23/13931/9db08f02b23e353bcd1597947e612079/basic-django.png
)