This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.2.0 instead.
build-wagtail
Dockerise a Wagtail project in place with one command. It generates a
Dockerfile, settings overrides and a compose.yml, copies the site's database
and media into ./data, and builds the image. The app runs on
granian.
Needs Docker with the compose plugin. The tool itself has no dependencies.
Install
uv tool install build-wagtail # or: pipx install build-wagtail
Usage
Run it from the Wagtail project root (where manage.py is):
build-wagtail example.org,www.example.org
docker compose up -d
docker compose exec web python manage.py createsuperuser
The first hostname is canonical. The site is served on 127.0.0.1:8000; put a
reverse proxy in front of it for TLS. By default the host's proxy is expected to
serve /static and /media from ./data, and the tool prints an example Caddy
config for that. With --caddy, a Caddy container serves them instead.
| Option | Default | |
|---|---|---|
--port |
8000 |
Localhost port the site is served on |
--caddy |
off | Run Caddy in a container for static/media |
--workers |
3 |
granian workers |
--python |
.python-version, else 3.13 |
Python version of the image |
--settings |
from manage.py, or <project>.settings.production |
Settings module to build on |
--no-build |
off | Write the files but skip docker compose build |
The project needs a uv.lock, pyproject.toml or requirements.txt.
What it writes
.env: secret key, hostnames and the container user. Created once, never overwritten.data/: the live database, media and collected static files. Seeded once, never overwritten. Back it up..wagtail-docker/andcompose.yml: regenerated on every run. Options aren't stored, so pass the same ones each time.
Metadata
Release files for build-wagtail 0.1.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 | Provenance | |
|---|---|---|---|---|
| build_wagtail-0.1.0.tar.gz | 6.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| build_wagtail-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.8 kB
Release files / build_wagtail-0.1.0.tar.gz
| Download URL | build_wagtail-0.1.0.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9144339058ce80b43e8fc68178acb4928a2eebb38da374adfd7df9235ea50a9
|
|
BLAKE2b-256 checksum How to use checksums |
95db657f54ec939d3ad21da94a9c93ce304663609b98457650f70e001eea14f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"NixOS","version":"26.11","id":"zokor","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / build_wagtail-0.1.0-py3-none-any.whl
| Download URL | build_wagtail-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cb234c8dc6f32d2c9454bb864d192e146dee86c7ce2eb7746b5de054ed6bba54
|
|
BLAKE2b-256 checksum How to use checksums |
d5755b406f7fb7e6370f85bea0bb4ffabe48383db433bb17ca3faee56d9c7e88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"NixOS","version":"26.11","id":"zokor","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for build-wagtail 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.