Yard
Push a repo to GitHub or Cursor Origin. Yard builds the container and serves the app over HTTPS.
Yard runs on one Ubuntu VM. It watches the forge, builds each push with Podman, and points Caddy at the new container. A git push is the whole deploy. There is no pipeline file and no dashboard.
Docs: stario.dev/yard
Quick start
On a fresh Ubuntu 26.04 LTS VM, as root, from a clone of this repo:
./install.sh --domain yard.example.com
The script prints an admin token. Then, on your laptop:
uv tool install staryard
yard login --url https://yard.example.com --token <token>
yard forge setup github # or: yard forge setup origin
cd my-app
yard app new --public app.example.com
git push
The command is yard. The PyPI name is staryard, because yard is taken. Python 3.14 or newer is required.
What an app needs
- A
ContainerfileorDockerfileat the repo root or inops/. Or acompose.ymlwith a serviceappon the networkyard. - A web process on port 8000.
- Settings from the environment.
yard env set KEY=VALUEwrites them. - Persistent files in
/data. That directory survives every deploy.
Yard is built for Stario apps, but it never looks inside the image. Any app in a container works.
Docs
The docs at stario.dev/yard read as a short book:
- The whole idea — Yard in one page: what each tool does and what Yard leaves out.
- One push, start to finish — follow a single commit from your laptop to a live container.
- Set up a host — a fresh VM to a working Yard in one script and a few commands.
- Your first app — the four rules an app follows, then one push.
- Day to day — logs, settings, domains, rollbacks, and cleanup.
- Your own compose file — workers, sidecars, healthchecks, and apps in any language.
- How it works — the internals: files, the check loop, the deploy container, Caddy, journald.
- CLI, API, Glossary — the lookup pages.
Develop
uv run pytest
uv run python -m app.server.main
just check # ruff, format, pyright, pytest
The code layout is in AGENTS.md. Changes are in CHANGELOG.md.
Metadata
Release files for staryard 0.7.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 | |
|---|---|---|---|---|
| staryard-0.7.0.tar.gz | 64.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| staryard-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 139.0 kB
Release files / staryard-0.7.0.tar.gz
| Download URL | staryard-0.7.0.tar.gz |
|---|---|
| Size | 64.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abdedd0bbe5aa7eecdad8af8b5f263be05aa62b10a8d75b9d2cefbb62416f3b5
|
|
BLAKE2b-256 checksum How to use checksums |
3c4a77eae6c642677db51c131fe6cedc49aa7e4db0b4fd819ffa79cf7ffb2e1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logRelease files / staryard-0.7.0-py3-none-any.whl
| Download URL | staryard-0.7.0-py3-none-any.whl |
|---|---|
| Size | 74.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
47a61f0da9c7e84be977ed82c3d8a30f77c15500a9542ea2247e1ec67ed8f5f0
|
|
BLAKE2b-256 checksum How to use checksums |
6ad87ecd3d5b56a8e8e0a74818d27edd567163ed65ea4206f1f45a6b346c09c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logSecurity for staryard 0.7.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for staryard-0.7.0.tar.gz
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 22, 2026.
Transparency logA 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.