Forge comes with a set of commands to facilitate working on your Django project as well as deploying it.
When in doubt, run
forge --help to see a list of available commands and
forge <command> --help to see a full list of arguments and options.
This page is just intended to give a quick overview of what's available!
Runs everything you need to work locally:
- The Django
- A Tailwind CSS compiler
- Postgres via Docker
Uses pytest to run your tests.
Invokes black and isort to format your Python code.
forge django <subcommand>
Passes through to the standard Django
forge django makemigrations.
Starts a gunicorn process and is intended to be used in your Heroku
Runs the Django system checks and also runs database migrations during the Heroku release phase.
forge quickstart template
Copies the default project structure into the current directory (except for
This is used by the quickstart but can also be used manually in advanced cases.
forge quickstart heroku
Creates a Heroku app and configures buildpackes, database, and environment variables.
Runs a set of pre-commit checks (including tests and formatting checks) and is automatically installed as a git hook during the quickstart.
When you (or a team member) clones an existing project,
forge pre-commit --install will be run automatically as part of the
forge tailwind compile
Automatically installs/updates Tailwind and compiles
--watch flag will watch for changes and automatically recompile.
--minify flag will minify the CSS.
forge tailwind compile --watch command is run automatically as a part of
forge tailwind update
Checks for and installs the latest version of Tailwind.
The installed version is saved (i.e. "locked") in
const FORGE_TAILWIND_VERSION = "<version>".