djinit

PyPI didn't allow the original name, so you'll find it as djinitx on PyPI

A CLI that scaffolds production-ready Django projects with DRF, JWT auth, API docs, and deployment configs - all through an interactive wizard. No more copy-pasting settings or wiring up apps by hand.

pipx install djinitx
djinit setup

Installation

# Recommended - isolated environment
pipx install djinitx

# Or with uv
uv tool install djinitx

# Or with pip
pip install djinitx

Requires Python 3.13+.

Usage

Create a project

djinit setup
# or
dj setup

The wizard walks you through these choices:

1. Project structure - Standard, Predefined (apps/ + api/), Unified (core/ + apps/), or Single Folder
2. Project name and directory
3. Database - PostgreSQL or MySQL; DATABASE_URL or individual env vars
4. Frontend tools - Tailwind CSS, HTMX, and/or Vite (optional)
5. Django apps - Name them; optionally nest under an apps/ package
6. CI/CD - GitHub Actions, GitLab CI, both, or none

When you're done, you have a fully configured Django project ready to run.

Add apps later

djinit app users products orders

Creates the apps, registers them in INSTALLED_APPS, and wires up URL includes.

Generate secret keys

djinit secret
djinit secret --count 5 --length 64

What You Get

Every project ships with:

• Split settings - base.py, development.py, production.py with sensible defaults
• Django REST Framework - With JWT authentication (access + refresh tokens)
• API documentation - Swagger UI at /docs/, ReDoc at /schema/
• CORS - Configured for local dev, locked down for production
• WhiteNoise - Static file serving, production-ready
• django-jazzmin - Modern admin interface
• Environment management - .env.sample with django-environ
• Deployment configs - Dockerfile, Procfile, runtime.txt
• CI/CD pipelines - GitHub Actions and/or GitLab CI
• Task runner - Justfile with common commands
• .gitignore - Python + Node defaults

Optional add-ons when selected:

Development workflow

just dev              # Start dev server
just migrate          # Run migrations
just test             # Run tests
just lint             # Lint with ruff
just format           # Format with ruff
just vite             # Start Vite dev server (if selected)
just dev-full         # Django + Vite together (if selected)

No just installed? These map directly to Django management commands.

Project Structures

Standard

myproject/
├── manage.py
├── myproject/          # Config module
│   ├── settings/       # base.py, development.py, production.py
│   ├── urls.py
│   └── wsgi.py
└── apps/               # Your apps (optional)
    └── users/

Predefined

myproject/
├── manage.py
├── config/             # Django config
│   ├── settings/
│   └── urls.py
├── apps/               # Business logic
│   ├── users/
│   └── core/
└── api/                # API routes
    └── v1/

Unified

myproject/
├── manage.py
├── core/               # Django config
│   ├── settings/
│   └── urls.py
└── apps/               # Main application package
    ├── admin/
    ├── models/
    ├── serializers/
    ├── views/
    ├── urls/
    └── api/

Single Folder

myproject/
├── manage.py
├── project/            # Configurable name
│   ├── settings/
│   ├── urls.py
│   ├── models/
│   ├── api/
│   └── wsgi.py

Environment Setup

cp .env.sample .env

SQLite works out of the box for development. Swap in your production database when you're ready.

Packages

API Endpoints

Contributing

Contributions are welcome. Open an issue or submit a PR.

1. Fork the repo
2. Create a feature branch (git checkout -b feature/whatever)
3. Make your changes and run just test
4. Submit a pull request

Match the existing code style - ruff linting and formatting are enforced.

License

MIT © Sankalp Tharu