Django Component for Diploi

A generic Django component ready to build your Django app.

This component was kickstarted running django-admin startproject djangoapp and it has DEBUG=true inside settings.py by default

To secure your Django app, you must update your SECRET_KEY in settings.py

By default all Django apps use SQlite, which you must update to use your database of choice inside settings.py

Uses the official python:3.13-alpine Docker image and Django 5.2.3

Operation

Development

Will run pip3 install -r requirements.txt --no-cache-dir when component is first initialized, and python3 manage.py runserver 0.0.0.0:8000 when deployment is started.

Production

Will build a production ready image. Image runs pip3 wheel --no-cache-dir --no-deps -r requirements.txt -w /wheels & pip3 install gunicorn --no-cache /wheels/* to install all necessary dependencies and python manage.py collectstatic --noinput to get all static files. Once the image runs, production is started using the command gunicorn djangoapp.wsgi:application --bind 0.0.0.0:8000 --workers 3 --log-level info

IMPORTANT

• You must generate a new SECRET_KEY for your own application
• Remember to update the database settings inside settings.py to match your own database config
• In production you must remember to update your settings.py, by changing DEBUG=false and if you want to use external CDNs for your static files, you will need to update the STATIC_ROOT
• For production and development, you are free to change the app server runner, so for example, if you prefer uwsgi you can change it directly on the Dockerfile for production and development

Links

• Django for production
• Django static files
• SECRET_KEY in Django
• Databases in Django
• Working with multiple databases in Django