A declarative, YAML-based homelab manager. labops is a CLI tool that simplifies, automates and standardizes the setup, configuration and maintenance of your homelab infrastructure using simple configuration files and powerful backend automation.
📖 Documentation · Getting started · Configuration · Commands
What it does
You describe your homelab once — the machines, the containers, the services they expose — and labops derives the rest from it.
hosts:
cprox:
hypervisor: proxmox
os: debian
ip: 10.0.10.3
lxc:
pihole:
ip: 10.0.10.5
os: debian
vmid: 105
web_services:
- proxy_name: pihole
port: 8080
That container is now three things at once: something labops update will patch, a pihole.lab DNS record, and a pihole.example.com route in your Caddyfile. Nothing was declared twice, so nothing can drift.
- Host management — setup and updates across Alpine, Debian and RedHat, via built-in Ansible playbooks
- Proxmox VMs & LXC — containers driven through the Proxmox host with
pct, so they need no sshd - Target selection — update an arbitrary slice of the lab by kind, OS, tag or position in the tree, ad-hoc or from a named set
- Docker stacks — sync compose files to a node, bring them up, pull newer images
- DNS automation — every node becomes a Pi-hole v6 record, derived from the inventory
- Reverse proxy — a Caddyfile rendered from your
web_services, with access lists and wildcard TLS - Wake — a magic packet for bare metal,
qm/pct startfor a Proxmox guest
Installation
pipx install labops
# or
pip install labops
Since labops is a standalone CLI tool, using pipx is highly recommended to isolate its dependencies.
Usage
Point it at a YAML config and go. labops finds homelab.yml by walking up from your current directory, the way docker compose finds a compose file.
labops --help # every available command
labops validate # is the config sound?
labops host list # what do I have?
labops update --all # patch everything
→ Full documentation, including a configuration reference and a JSON Schema for editor autocompletion.
Development
See the development guide for the full setup. In short:
uv sync
source .venv/bin/activate
just check # lint + type-check
just test # pytest
just docs-serve # preview the docs site
The project uses Dev Containers for a consistent environment and uv for package management. Releases are automated with release-please; the package is published to PyPI by GitHub Actions, not by hand.
Metadata
Release files for labops 0.13.3
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 | Actions |
|---|---|---|---|---|
| labops-0.13.3.tar.gz | 353.1 kB | Without provenance | Details for labops-0.13.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| labops-0.13.3-py3-none-any.whl | Python 3 | none | any | Details for labops-0.13.3-py3-none-any.whl |
Total release size: 500.2 kB
Release files / labops-0.13.3.tar.gz
| Download URL | labops-0.13.3.tar.gz |
|---|---|
| Size | 353.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bca37d63a009ed2658e2b9f9e62b8d57f8420ac17f410daa3a9d728d4fe49143
|
|
BLAKE2b-256 checksum How to use checksums |
9d2b0c7b19f21a928d61698e58a7a1da46bc4438d540779022e5dfb06129eb65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / labops-0.13.3-py3-none-any.whl
| Download URL | labops-0.13.3-py3-none-any.whl |
|---|---|
| Size | 147.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea3751b56decfe5554b9b3df3e7cc45f405ceb9b094541bcefac740789c0c34f
|
|
BLAKE2b-256 checksum How to use checksums |
69f4c2d5bf26b577793b660e07b55900fb9808f163cef581264dc4a027dfecab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for labops 0.13.3
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.