Documenting the craft of stacking things so they remain stacked. For a very long time.
These pages are generated in the component repositories and copied in here verbatim. Nothing in this directory is edited by hand: a correction belongs in the repository the page came from, and arrives here on the next sync.
Their titles, one-line descriptions and sort order are all derived from the pages themselves, so adding one is a copy and a run of make-docs-index.py.
kernel and boot-entry custody for atomic, slice-based systems
configuration for boot-manager(8)
build the system TLS CA trust store
instance configuration format read by instance-setup(8)
web UI and HTTP proxy for the dispatcher build host
operator policy for the dispatcher build host
ban hosts that abuse services, by watching the systemd journal
rule files for flagger(8)
configuration file for flagger(8)
read a cloud config-drive into systemd credentials
Ur Project package and composition CLI
remove installed packages no selection root still reaches
build a recipe directory into a signed local repository
produce or install an offline .pkgtar bundle
how pkg orders repositories and decides which build is current
report whether updates are available, changing nothing
print a shell completion script
compose a closure into a deployable artifact
list the transactions this machine committed, or show one
print details of a manifest, by name or by path
install packages and sets
create the key pkg build signs with
report what is installed under which license, and print the
list installed packages, or everything the chain makes current
list installed package sets, or every set in the chain
update an air-gapped system by hand-carried bundle
hold packages at a build, or release them
local pins: packages this machine resolves to an exact build
verify, reproduce, or fetch the sources of a published build
print details of an installed package
remove installed packages, or drop a set root
restore an installed package's drifted files from its payload
add, remove, enable, disable and list configured repositories
repository drop-in configuration for pkg
on-disk and URL layout of an Ur Project repository
return the installed set to a recorded transaction
emit a software bill of materials for the installed set
search the repository chain by name, capability or file
list or inspect package sets published across the chain
package sets and selection roots
sign a package manifest
pre-download the payloads an upgrade would install
on-disk client state of an Ur Project system
subpackages, content classes, and what a bare name means
run or list the system trigger ruleset
converge the installed set onto what the chain pins
verify the on-disk state of installed packages
verify the signature on a package manifest
system-wide client configuration for pkg
