djangocloud-cli
Command-line client for DjangoCloud. Standard library only.
pip install djangocloud-cli # then add "djangocloud_cli" to INSTALLED_APPS
python manage.py djangocloud login
python manage.py djangocloud deploy
python manage.py djangocloud logs -f
python manage.py djangocloud help
A standalone djangocloud script is installed too (same commands, no manage.py), for when your settings won't load.
Status: early. help, login, logout, whoami, link, unlink and the interactive setup in deploy work
(they need the DjangoCloud API). Uploading, building and deploying, logs and status are next.
First run
$ python manage.py djangocloud deploy
You're not signed in yet.
Open https://djangocloud.dev/dashboard/cli/?code=ABCD-EFGH and check that the code is ABCD-EFGH.
✓ Signed in as you@example.com
? Which project is this? (arrow keys)
? Server size Nano 0.25 vCPU, 0.5 GB RAM $10/month
? This will cost $10 per month. Continue? Yes
✓ Linked to my-shop (.djangocloud/config.json)
.djangocloud/config.json says which project this folder deploys to. It holds no secrets and is git-ignored by a
.gitignore inside the folder. Later runs skip every prompt.
CI (GitHub Actions)
Create a token under Command line → Token for CI in the dashboard and store it as the repository secret
DJANGOCLOUD_TOKEN. --no-input makes the CLI fail with a clear message instead of ever prompting or opening a browser.
- run: pip install djangocloud-cli
- run: python manage.py djangocloud deploy --no-input --project my-shop
env:
DJANGOCLOUD_TOKEN: ${{ secrets.DJANGOCLOUD_TOKEN }}
Configuration
| Variable | Purpose |
|---|---|
DJANGOCLOUD_TOKEN |
API token for CI; takes precedence over the stored login |
DJANGOCLOUD_NO_INPUT |
Same as --no-input (set it to 1) |
DJANGOCLOUD_API |
API base URL (default https://djangocloud.dev/api/v1) |
The token from login is stored in ~/.config/djangocloud/credentials.json (mode 600).
Development
uv sync
uv run pytest
uv run ruff check
1 maintainer
Metadata
1 maintainer
Release files for djangocloud-cli 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| djangocloud_cli-0.1.1.tar.gz | 28.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| djangocloud_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.2 kB
Release files / djangocloud_cli-0.1.1.tar.gz
| Download URL | djangocloud_cli-0.1.1.tar.gz |
|---|---|
| Size | 28.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8546dba10a94812b507cf47aa9321b8a4e126b2ca3aca9607555b85274722da
|
|
BLAKE2b-256 checksum How to use checksums |
b12c524ebc9248a6706b388b539cc5ffc73601ac486d1fbac5011b999c5dedf8
|
| 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 Oct 5, 2026.
Transparency logRelease files / djangocloud_cli-0.1.1-py3-none-any.whl
| Download URL | djangocloud_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
175731662032f0f2e6f88ca5984b65bb3f9cde39fb08e17a1d600e09f095434d
|
|
BLAKE2b-256 checksum How to use checksums |
b18ca37d52022bfb77070a2ca96ce503ce04441601cba88b665aae9627b2b290
|
| 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 Oct 5, 2026.
Transparency log
