dvt (devtemplate)
Dev-style named devcontainer templates, built and run directly via Docker or Podman.
Templates are fetched from jesserobertson/devcontainers's templates/ directory.
Install
pipx install dvt-cli
For a local checkout instead (e.g. to track main), use pipx install ./dvt from the
repo root.
Usage
dvt sync
dvt feature list
dvt init ./my-project
dvt feature add fastapi # run from inside a project with .devcontainer/devcontainer.json
dvt feature add agent
dvt up my-project
dvt ssh my-project
dvt run -n my-project pytest -q # run one command inside the workspace, exit with its status
dvt info # from inside my-project - no name needed
Development
dvt is developed inside the jesserobertson/devcontainers
monorepo, at dvt/. Clone that repo and run the commands below from dvt/.
The pixi default environment (what pixi run uses) carries pytest and
hypothesis for the dev loop. A separate runtime environment
(pixi run -e runtime ...) has none of that test tooling, for anyone who
wants to confirm the package installs cleanly without it — actual
distribution to end users is via pipx install, not pixi, so this is a
verification aid rather than the real install path.
pixi install
pixi run pytest
Tasks
Each task below is a pixi run wrapper script; the ones with sub-commands
dispatch on the first extra argument (e.g. pixi run test unit), so pixi run <task> alone isn't a valid invocation for those. pixi <task> (without
run) never works — pixi requires the run verb to invoke a task.
| Task | Sub-commands | What it does |
|---|---|---|
pixi run quality |
check, typecheck, lint, format [--check], fix, coverage [--html] |
mypy + ruff lint/format, or auto-fix both with fix |
pixi run test |
unit, integration, all, fast, clean |
pytest by tier — integration needs a real Docker/Podman runtime and isn't included in all/fast |
pixi run docs |
serve [--port], build [--strict], status, clean |
mkdocs site under docs/ — serve runs a local dev server at localhost:8000 |
pixi run check-all |
— | test all + quality check, for a full pre-push sanity check |
pixi run clean |
— | test clean + docs clean |
Metadata
Release files for dvt-cli 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dvt_cli-0.4.0.tar.gz | 167.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dvt_cli-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 251.8 kB
Release files / dvt_cli-0.4.0.tar.gz
| Download URL | dvt_cli-0.4.0.tar.gz |
|---|---|
| Size | 167.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
658e024b346713eb84e9dce49a3e90020e7503505bdbe0c9c003181befde5b4a
|
|
BLAKE2b-256 checksum How to use checksums |
8a78735063ddb3f9d2ef7d75c9f85f24b3dbac694e2b32bb7c9f7394d50539b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / dvt_cli-0.4.0-py3-none-any.whl
| Download URL | dvt_cli-0.4.0-py3-none-any.whl |
|---|---|
| Size | 83.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d5a95bccdcf2f502c636fa8b6690f6d28e6e8d40df7be2a00d85afb5730081ac
|
|
BLAKE2b-256 checksum How to use checksums |
6517532c916bec8d621cad438cf000b08d27f74f741c4bdd8d1c075a07cc724f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency log