Yard
Yard runs each app in its own container. You push a repo. Yard builds the Containerfile and starts the container. Caddy sends public traffic to that container.
Slot
A slot is one app. The container name is the slot name.
A slot points at one repo and one branch. The repo must already contain one of these files:
ContainerfileDockerfileops/Containerfileops/Dockerfile
A push to that branch builds the image and starts the container. Yard removes the slot when that branch is merged or deleted.
--every 5m makes a job. Yard keeps one run at a time. The next run uses the same container name.
Host
Yard keeps its files under /srv/yard. Each slot keeps its files under /srv/yard/data/<name>.
Caddy listens on port 8443. The host forwards port 443 to that port. Yard posts the Caddy config to a Unix socket.
CLI
The command is yard. The package name is staryard. PyPI already has a package named yard.
uv tool install staryard
yard --version
Python 3.14 is required. yard login stores the host and the token on this computer.
staryard[server] installs the server libraries. The host still runs the container image.
Install
Run the script on the VM as root. A second run repairs a partial install. A healthy Yard container stays in place.
./install.sh --domain yard.example.com
The script installs ghcr.io/bobowski/yard:latest. A finished run has checked the health page, the container route, and the path to Let's Encrypt. With --domain it also checks the certificate and https://<domain>/health.
The script prints an admin token. Log in from your computer:
yard login --url https://yard.example.com --token <token>
The package must be public. A private package needs podman login ghcr.io on the VM before the script.
GitHub Actions builds the image when this directory is the root of the repo. The workflow publishes ghcr.io/bobowski/yard:latest for linux/amd64.
Update Yard
yard update pulls ghcr.io/bobowski/yard:latest and swaps the Yard container. yard rollback starts the previous image.
A repo on this host replaces that image:
yard settings --self-repo yard
yard update
Clear the repo to return to the image:
yard settings --self-image
yard update
Add an app
Run this in the app directory. The directory name is the repo name and the slot name.
yard init --domain heldso.example.com
git push -u yard main
yard init makes a git repo when the directory has none. It makes the Yard repo and the slot. It adds a git remote named yard. It does not push.
Pass --domain for a public host. Pass --every 5m for a job. One of them is required. --name sets the repo name and the slot name. --repo and --slot set one each.
yard repo new, yard repo link, and yard slot new do those steps one at a time.
Commands
Run yard to see every command. These are the common ones:
yard slot listshows each slot, its data size, and how long the last build took. The last row is the host total.yard slot edit <name>changes the slot file.yard slot logs <name>reads the container log.yard settingssets the public host, the Caddy email, and the Yard image.
A terminal prints text. Any other stdout prints JSON.
Develop
The server command is python -m app.main.
uv run pytest
STARIO_LOOP=uvloop uv run python -m app.main
Metadata
Release files for staryard 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 | |
|---|---|---|---|
| staryard-0.1.0.tar.gz | 41.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| staryard-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.4 kB
Release files / staryard-0.1.0.tar.gz
| Download URL | staryard-0.1.0.tar.gz |
|---|---|
| Size | 41.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7278faf5cb167a46623d637e981d4892a5ac8c5b413a0a20ff4f0cf3bbd75b6
|
|
BLAKE2b-256 checksum How to use checksums |
d997685e3404526b86cb28978e050975925eb447194d89909ee980d1c9267a90
|
| 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 Oct 7, 2026.
Transparency logRelease files / staryard-0.1.0-py3-none-any.whl
| Download URL | staryard-0.1.0-py3-none-any.whl |
|---|---|
| Size | 46.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e4d35f15ef5a26e2480e65ed5f6baea2096313cab0f4cce81f4d6bb3ebbe6a7
|
|
BLAKE2b-256 checksum How to use checksums |
5061bfdc9766ae9e0524a0b8374b55ab41ee3234e26148ed1996c37d474b2eb5
|
| 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 Oct 7, 2026.
Transparency log