DjangoGCP
Helps you to run Django on Google Cloud Platform:
- Storage (including direct uploads)
- Events (PubSub)
- Tasks (ad-hoc and scheduled)
- Logging (pretty colours and labels) and
- Error Reporting.
Read the documentation here.
This app is maintained by Octue - we're on a mission to help climate scientists and energy engineers be more efficient. Find out more. If you need some help implementing django-gcp, or wish to sponsor a feature or any of the issues on the board, we can help! Raise an issue or contact us.
Are you from GCP??
If so, get in touch for a chat. We're doing fun things with Google Cloud. Way funner than boring old django... :)
All the ❤️
This app is based heavily on django-storages, django-google-cloud-tasks and uses the django-rabid-armadillo template. Big love.
Contributing
It's pretty straightforward to get going, but it's good to get in touch first, especially if you're planning a big feature.
Set up
Open the project in codespaces, a vscode .devcontainer (which is configured out of the box for you) or your favourite IDE or editor (if the latter you'll need to set up docker compose yourself).
Create a file .devcontainer/docker-compose.developer.yml. This allows you to customise extra services and volumes you make available to the container.
For example, you can map your own gcloud config folder into the container to use your own credentials. This example will get you going, but you can just leave the services key empty.
version: "3.8"
services:
web:
volumes:
- ..:/workspace:cached
- $HOME/.config/gcloud:/gcp/config
environment:
- CLOUDSDK_CONFIG=/gcp/config
- GOOGLE_APPLICATION_CREDENTIALS=/gcp/config/your-credentials-file.json
Initialise gcloud CLI
To sign in (enabling use of the gcloud CLI tool), do:
gcloud config set project octue-django-gcp
gcloud auth login
Run the tests
Run the tests:
pytest .
We use pre-commit to ensure code quality standards (and to help us automate releases using conventional-commits). If you can get on board with this that's really helpful - if not, don't fret, we can help.
Use the example app
You can start the example app (which is useful for seeing how django-gcp looks in the admin.
Initially, do:
python manage.py migrate
python manage.py createsuperuser
# make yourself a user account at the prompt
Then to run the app, do:
python manage.py runserver
...and visit http://localhost:8000/admin/ to sign in.
Update the docs
We're pretty good on keeping the docs helpful, friendly and up to date. Any contributions should be fully documented.
The docs are written in Markdown and built with Zensical. To develop them with live reload, start the dev server and open the URL it prints:
uv run --group docs zensical serve
Read the Docs builds and publishes the site from .readthedocs.yaml on each push. Redirects
from the old Sphinx page URLs are mapped in scripts/rtd_redirects.toml; if you change the
docs structure, add redirects there and sync them with python scripts/sync_rtd_redirects.py.
1 maintainer
Metadata
1 maintainer
Release files for django-gcp 0.26.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_gcp-0.26.3.tar.gz | 82.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_gcp-0.26.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 157.8 kB
Release files / django_gcp-0.26.3.tar.gz
| Download URL | django_gcp-0.26.3.tar.gz |
|---|---|
| Size | 82.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9526276296622fb3d9ed61fdc7b4369330aa2f8955abe5b286cd29aa1ddf96e
|
|
BLAKE2b-256 checksum How to use checksums |
7005d78692eb8af939d1f96bcfdedfadc8910e8c63815f1d95b757514ee74f68
|
| 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 Sep 20, 2026.
Transparency logRelease files / django_gcp-0.26.3-py3-none-any.whl
| Download URL | django_gcp-0.26.3-py3-none-any.whl |
|---|---|
| Size | 75.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22c510ef9697ad523086f47fd8dc0347d61dc16dadc4b4d91831732e434e761f
|
|
BLAKE2b-256 checksum How to use checksums |
f2f96435da06d66a23384d1dd7bbe56a39152432098d3911f3c90a5e38328517
|
| 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 Sep 20, 2026.
Transparency log
