This release is a pre-release and may not be stable for production use.
bella-baxter-django
Django integration for the Bella Baxter secrets management platform. Automatically loads secrets from Bella Baxter and makes them available throughout your Django app.
Installation
pip install bella-baxter-django
Quickstart
# settings.py
INSTALLED_APPS = [
...
'bella_baxter_django',
]
BELLA_BAXTER_API_KEY = 'bax-...'
BELLA_BAXTER_URL = 'https://api.bella-baxter.io' # optional, this is the default
# anywhere in your code
from bella_baxter_django import get_bella
client = get_bella()
secrets = client.get_all_secrets()
db_url = secrets.secrets['DATABASE_URL']
How it works
get_bella() returns a shared BaxterClient instance, initialised lazily on first call
and cached for the lifetime of the process. Adding 'bella_baxter_django' to INSTALLED_APPS
triggers eager initialisation at Django startup via BellaBaxterConfig.ready(),
so the first request doesn't bear the connection cost.
Configuration
| Setting | Required | Default | Description |
|---|---|---|---|
BELLA_BAXTER_API_KEY |
✅ | — | API key (bax-...) |
BELLA_BAXTER_URL |
❌ | https://api.bella-baxter.io |
Base URL of the Baxter API |
Using secrets in views
from django.http import JsonResponse
from bella_baxter_django import get_bella
def health(request):
bella = get_bella()
secrets = bella.get_all_secrets()
return JsonResponse({'db': secrets.secrets.get('DATABASE_URL', 'not set')})
Using secrets in settings.py
# settings.py — bootstrap secrets before Django fully loads
import os
from bella_baxter import BaxterClient, BaxterClientOptions
_bella = BaxterClient(BaxterClientOptions(
baxter_url=os.environ.get('BELLA_BAXTER_URL', 'https://api.bella-baxter.io'),
api_key=os.environ['BELLA_BAXTER_API_KEY'],
))
_secrets = _bella.get_all_secrets().secrets
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql',
'HOST': _secrets['DB_HOST'],
'NAME': _secrets['DB_NAME'],
'USER': _secrets['DB_USER'],
'PASSWORD': _secrets['DB_PASSWORD'],
}
}
Authentication
Generate an API key via the CLI or the Bella WebApp:
bella api-keys create --env production --name "Django Production"
Set it in your environment and reference it in settings.py:
export BELLA_BAXTER_API_KEY="bax-..."
1 maintainer
Release files for bella-baxter-django 0.1.1rc98
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bella_baxter_django-0.1.1rc98.tar.gz | 3.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bella_baxter_django-0.1.1rc98-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.0 kB
Release files / bella_baxter_django-0.1.1rc98.tar.gz
| Download URL | bella_baxter_django-0.1.1rc98.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
827f77a6c5d3ae1c7b5138513027656ab3bbd14079df581ffedf4dc381f50238
|
|
BLAKE2b-256 checksum How to use checksums |
ee94e0921b3278389b94545142e2eebd50409ee591b3f56b6f4ded79cdf0c557
|
| 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 10, 2026.
Transparency logRelease files / bella_baxter_django-0.1.1rc98-py3-none-any.whl
| Download URL | bella_baxter_django-0.1.1rc98-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
387db306a167d76b28e466861e6dca82c2c8f7cd376656c3cbbfdd59ae089b06
|
|
BLAKE2b-256 checksum How to use checksums |
10cf8d702eb65b8e7497b4c0936845ac75c1d439e9df4627a2d7397db6959506
|
| 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 10, 2026.
Transparency log
