Understanding Django's file Structure

I am a developer from Delhi, India
Search for a command to run...

I am a developer from Delhi, India
No comments yet. Be the first to comment.
In this series, I will walk you through everything needed to become a Django Developer. However, the pre-requisite of this series, is that you are well versed with Python.
Each application you write in Django consists of a Python package that follows a certain convention. Django comes with a utility that automatically generates the basic directory structure of an app, so you can focus on writing code rather than creati...
DISCLAIMER: This might not be the most well-written article since I haven't written in a while and I just wanted to get back to writing with a short article about my experience of the day, so sorry about that I previously used this repository for my...

The release of NextJS 13 brought about a plethora of new and impressive features, with one standout being the updated data fetching and management process. The fetch API replaced the more complicated functions, including getServerSideProps, getStatic...

Looking for a safe and reliable way to authenticate users? Consider implementing magic links. They offer a secure alternative to traditional passwords and can help mitigate the risk of password leaks and forgotten passwords. Magic Link authentication...

Neovim is a powerful text editor that can be customized with plugins to enhance its functionality. In this article, we will explore the top 10 essential Neovim plugins. These plugins can help improve your Neovim experience by adding features such as ...

A type-safe and zero-runtime version of Tailwind CSS

This article is part of a series regarding Complete Beginners Guide to Django. So, if you haven't seen the first part of this series, check it out at
So, after following the instructions in the first part, your file structure should like this
.
├── db.sqlite3
├── livecode247
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-38.pyc
│ │ ├── settings.cpython-38.pyc
│ │ ├── urls.cpython-38.pyc
│ │ └── wsgi.cpython-38.pyc
│ ├── asgi.py
│ ├── settings.py
│ ├── urls.py
│ └── wsgi.py
└── manage.py
└── myenv
└── *
manage.py is basically the main file of our whole project which runs our application. This file is rarely edited manually if not never. I have never had to edit it for anything
db.sqlite3 is the default sqlite database created by Django for our use. We will be using this database to store data regarding our application like blogs, the content inside them, etc.
An empty file file that tells Python that this directory should be a Python package
This directory is just some stuff which is generated by Django for caching stuff. It's not of much use to us
A file which helps us to deploy our app with ASGI-compatible web servers.
A file which helps us to deploy our app with WSGI-compatible web servers.
Stores all the settings and configurations for our projects. We will be updating this quite frequently
Stores all the urls of the site and what view they point to.
In the next part of this series, we will be talking about how to create an app in our project and add a basic hello world page.