Visit djangoplay.org ↗
astwire / Deployment / Deployment
DocsastwireDeploymentDeployment

Deployment

astwire is distributed as a compiled native binary, not a package installed into a Python environment. Its deployment lifecycle is:

1 min readApplies to v1.0.0
text
source repository (GitLab, private)
      │
      ▼
unit tests (pytest)
      │
      ▼
Nuitka standalone --onefile compilation
   (macOS arm64 / Linux amd64 / Linux arm64 / Windows amd64)
      │
      ▼
GitLab Generic Package Registry
   (versioned + latest, per platform asset)
      │
      ▼
Cloudflare R2 sync
   (installers/ + install.sh + install.ps1 + manifest)
      │
      ▼
install.djangoplay.org  (302 redirect to R2)
      │
      ▼
curl | bash   /   irm | iex
      │
      ▼
astwire  (on $PATH)

There is no server component and no database — "deployment" here means getting a compiled binary onto a public download surface, not standing up a running service.

  • local-development.md — environment setup, running tests, compiling locally
  • binary-distribution.md — the full cross-platform build matrix, Cloudflare R2 sync architecture, and GitLab CI/CD pipeline
  • package-release.md — the condensed release checklist and Makefile targets used to cut a release