CLI

When you install a DjangoKit project, a console script named djangokit (dk for short) is also installed. Here's how you would run a Django management command:

uv run dk manage <command>

And here's how you'd add a new page route and a model:

dk add-page some_path
dk add-model MyModel

If you don't want to type uv run before dk commands all the time, you can activate your project's virtualenv in the usual way by sourcing or running the activate script (e.g., source ./.venv/bin/activate.

One thing you'll notice is that there's no manage.py script in a DjangoKit project (although you could add one if you needed to). One reason for this is so that all commands are run consistently using dk .... Additionally, the dk script makes it easy to switch configuration by passing a --env option like so: dk --env staging ....

NOTE: You can run all the built-in and custom Django management commands using dk manage <command>.

It's also much easier to add custom Django management commands to the dk script than it is to use Django's builtin facilities for adding commands. This is because the DjangoKit CLI is built on top of Typer, which makes writing commands much simpler.