Getting Started
Install SOW, publish a working repository in five minutes, and learn the model behind it.
SOW Documentation
Create and manage APT / YUM package repositories with a single self-contained binary.
SOW is a self-contained package repository manager built by Pigsty.
It ships as one static Go binary that creates and maintains APT (DEB) and YUM (RPM)
repositories on Linux and macOS — no createrepo_c, no dpkg-scanpackages, no reprepro,
no daemon.
It operates in two isolated modes:
- Plain mode —
sow createturns any directory of.rpm/.debfiles into a flat, servable repository, deterministically and in place. - Managed mode — a workspace with Debian-style package pools, per-architecture views, GPG signing, membership policies, transactional builds, and a full audit trail.
Getting StartedInstall SOW, build your first flat repository in five minutes, and learn the core concepts.
TutorialsEnd-to-end walkthroughs: YUM and APT repositories, GPG signing, serving with Nginx, and
migrating from createrepo_c or reprepro.
FeaturesHow SOW works: the Plain and Managed engines, package pools and architecture views,
membership policy, signing, transactions, and auditing.
DesignArchitecture and decision records: ownership, the 0.3 single-payload model, publication,
compatibility boundaries, and the evolution from v0.2.
ReferenceComplete CLI reference,
sow.yml configuration, package reference grammar, exit codes,
repository layouts, and the compatibility matrix.Where to begin
| If you want to… | Read |
|---|---|
| Get a repository online right now | Quick Start |
| Understand the mental model first | Core Concepts |
| Build a production YUM / APT repository | Tutorials |
| Understand architectural decisions and version boundaries | Design |
| Replace an existing createrepo_c / reprepro pipeline | Migration guide |
| Look up a command or config field | Reference |
Tutorials
End-to-end walkthroughs that take a pile of packages all the way to a signed repository your clients can install from.
Features
How SOW works and why it is built this way: execution paths, pool projection, policy, signing, transactions, and audit.
Design
The architectural decisions behind SOW: ownership, repository layout, publication, compatibility, and version evolution.
Reference
Command syntax, configuration schema, on-disk layout, exit codes, JSON output, and the tested compatibility matrix.