ZacharyZhang-NY/omarchy-pkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Run host operations locally when this machine is the build host

Browse Source 
Release commands now work from anywhere: on_repo_host (the published database
living in this checkout) routes build triggers, advances, and promotion to
local execution; other machines go over ssh to the configured destination.
The host setting is any ssh destination — root@<ip>, root@<hostname>, or an
~/.ssh/config alias — resolved from --host, OMARCHY_REPO_HOST, then the
one-line .repo-host file. doctor reports which mode applies, and the README
documents the format and precedence. All host connections are plain ssh.
This commit is contained in:
Ryan Hughes
2026-08-27 01:10:33 -04:00
parent a5cafb291c
commit 52475c4bbc
3 changed files with 75 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+24 -5
View File
@@ -467,12 +467,31 @@ bin/repo advance --from rc --to stable
Neither package is on the `fast` ring, and `bin/omarchy-pkgs` never touches
stable — promotion is always this explicit step.
### Build trigger
### Build trigger and the build host
After pushing, the command triggers the build host over ssh when
`OMARCHY_REPO_HOST` is set (env var, or a hostname in the git-ignored
`.repo-host` file). Without it, the 6-hourly auto-release timer picks up the
change on its own.
Release commands run from anywhere. When the machine you are on **is** the
build host (detected by the published database living in this checkout), host
operations — build triggers, `advance`, promotion — execute locally. From any
other machine they go over ssh to the configured host; without a configured
host, the exact commands to run are printed and the 6-hourly auto-release
timer serves as the backstop.
The host setting is any destination `ssh` accepts, resolved in this order:
1. `--host <dest>` on the command
2. `OMARCHY_REPO_HOST` environment variable
3. the git-ignored `.repo-host` file (one line; `#` comments allowed)
The server layout lives under `/root`, so the value is `root@<ip>`,
`root@<hostname>`, or — nicest — a `Host` alias from `~/.ssh/config` that
carries the user, key, and port:
```
# .repo-host
root@pkgs.example.com
```
All connections are plain ssh; nothing else is used to reach the host.
## Directory Structure