A Django 5.2 LTS starter on Python 3.12 and PostgreSQL for developers who want accounts done before they write their first model, with no Node.js and no front-end build. It covers email sign-up, sign-in, sign-out and password reset on Django's own auth views, a custom user model, the Django admin, a projects example scoped to each user, a database health check and a Dockerfile that runs Gunicorn and applies migrations on start.
by Light CloudFull-stack


Every setting is read from the environment in config/settings.py, and the usual first edits are templates/home.html, the colour tokens in static/app.css and the projects app, whose OwnProjects mixin is the pattern for your own models: another user's row is a 404, not a 403. Gunicorn preloads config/wsgi.py, which applies migrations while holding a PostgreSQL advisory lock and closes its connection before the workers fork, so several instances starting together take turns. The attempt limit is counted in each Gunicorn worker's own memory, so with several workers or instances the real limit is higher until you point CACHES at a shared backend such as the database or Redis. Open the app and create your account straight after deploying, because the first account is the one that can use the admin. Reset links use APP_URL, which Light Cloud sets at each deploy; on other hosts set it yourself, or the links take their host from the request, which a forged X-Forwarded-Host header can change. Without EMAIL_HOST every email goes to the log, SMTP delivery has not been tested against a real provider, and the projects list has no pagination yet.
Django's documentation recommends a custom user model for every new project, because switching later means rewriting migrations. accounts.User signs in with an email address and has no username, and you can add fields such as a display name with a normal migration.
Set DATABASE_URL, for example postgresql://user:password@host:5432/db?sslmode=require. config/settings.py parses it without an extra package and passes only libpq's own parameters to psycopg 3, so URLs written for Node.js drivers work too.
To the log. Django's console email backend prints each email, including the reset link, to the terminal on your machine and to the container log in Docker and on Light Cloud. Set EMAIL_HOST and the other EMAIL_* variables to send them over SMTP.
Run python manage.py startapp, add a model with a foreign key to settings.AUTH_USER_MODEL and copy projects/views.py: the OwnProjects mixin is what keeps each user to their own rows. Then run makemigrations, add the URLs and templates, and register it in the admin.
Yes. It has no Light Cloud code: build the Dockerfile on any Docker host, or run collectstatic and gunicorn config.wsgi:application on any Python 3.12 host, with DATABASE_URL, DJANGO_SECRET_KEY and APP_URL set.


Start a Laravel app with sign-up and password reset on PostgreSQL, without a starter kit


Start a Rails 8 app with sign-up and password reset on PostgreSQL, with no Node.js build
Start a Python CRUD API on PostgreSQL with Django REST framework, migrations and tests