Frameworks solution
Run Django Locally with FlyEnv
Django projects often pair Python with a database and, depending on the application, services such as Redis and a reverse proxy. FlyEnv keeps those local services manageable around the Django project.
Local project stack
Services FlyEnv can manage around Django
About Django
Django is a high-level Python web framework built around reusable apps, a mature ORM, migrations, forms, authentication, and an automatic administration interface. It is particularly suited to database-backed sites whose business rules and content models evolve together.
Development normally begins inside a Python virtual environment with manage.py coordinating the project. Deployable applications may also need a relational database, static and media handling, and Celery processes when asynchronous work is part of the design.
Core capabilities
- Django ORM
- Admin Site
- Migrations
- Forms
- Authentication
- ASGI Support
Common use cases
- Editorial and membership websites
- Data-heavy business applications
- Back-office tools built around the admin
- Marketplace or directory platforms
- APIs paired with Django REST Framework
A Django project is more than runserver
manage.py coordinates framework tasks, while project choices determine which supporting processes are needed locally.
- Python environment
- A venv, uv, or Poetry environment keeps Django and project dependencies isolated.
- PostgreSQL or MySQL
- Production-like Django projects commonly use a relational database and apply schema changes with manage.py migrate.
- Static and media files
- Templates, collected static assets, and user uploads require separate local paths and configuration.
- Celery broker and worker when configured
- Redis or RabbitMQ and a Celery worker are relevant only for projects that run background tasks.
Project resources
For installation commands, supported versions, and project-specific configuration, refer to the official Django documentation.
Typical local stack
The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.
How FlyEnv helps
Select Python per project
Keep projects that target different Python versions separate.
Run the chosen database
Use PostgreSQL or MySQL when the Django settings require it.
Keep Redis optional
Start Redis only for projects that use its cache or async features.
Configure a local address
Use a web server, local domain, and HTTPS when the workflow needs them.
Set up the local environment
Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.
- 1Install and configure the Django project according to the official Django documentation.
- 2Choose the Python runtime expected by the project.
- 3Start the database configured in the project settings.
- 4Start Redis only when the project uses it.
- 5Configure a local web server, domain, and HTTPS when appropriate.
- 6Use a Startup Group to keep the project services together when useful.
Related solutions
Ready to run Django locally?
Use FlyEnv to manage the runtimes, databases, web servers, and services around your local Django environment.