David Heinemeier HanssonandClaude Opus 5
51004999e7
bin/build asks the local repository database which packages are already built. A build machine has no such database, so every package looks out of date: an unscoped 'bin/repo deploy' on this laptop would have built all 108 packages and published them. Verified with a dry run. deploy now refuses to run unscoped when that database is absent, and push refuses the same combination under --yes, where nobody would see the list it prints before publishing. Both are allowed on the repository host, which has the database that makes the comparison meaningful. Also states the split in the README: build, push and deploy are the three commands that may run off the repository host; everything else works on the published tree directly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
53 lines
1.7 KiB
Bash
53 lines
1.7 KiB
Bash
# Resolving the Omarchy repository host
|
|
#
|
|
# One machine both serves pkgs.omarchy.org and runs the scheduled builds. The
|
|
# commands that reach it are doing repository work — uploading artifacts,
|
|
# signing, publishing — so the setting is named for the repository rather than
|
|
# for building, which happens on whatever machine the operator prefers.
|
|
|
|
# Usage: resolve_repo_host [explicit-host]
|
|
# Prints the host, or nothing when none is configured.
|
|
resolve_repo_host() {
|
|
local explicit="${1:-}"
|
|
|
|
if [[ -n "$explicit" ]]; then
|
|
echo "$explicit"
|
|
return 0
|
|
fi
|
|
|
|
if [[ -n "${OMARCHY_REPO_HOST:-}" ]]; then
|
|
echo "$OMARCHY_REPO_HOST"
|
|
return 0
|
|
fi
|
|
|
|
if [[ -f "$BUILD_ROOT/.repo-host" ]]; then
|
|
# Ignore blank lines and comments so the file can be annotated.
|
|
local value
|
|
value=$(grep -vE '^\s*(#|$)' "$BUILD_ROOT/.repo-host" | head -1 | tr -d '[:space:]')
|
|
if [[ -n "$value" ]]; then
|
|
echo "$value"
|
|
return 0
|
|
fi
|
|
fi
|
|
|
|
return 1
|
|
}
|
|
|
|
# True when this checkout holds the published repository, which in practice means
|
|
# this machine is the repository host. Every other command in bin/ works on that
|
|
# tree directly; build, push and deploy are the ones that may run elsewhere.
|
|
#
|
|
# The database is the marker rather than the directory: bin/build creates empty
|
|
# mirror directories as a side effect, so their presence proves nothing.
|
|
on_repo_host() {
|
|
[[ -f "$REPO_DIR/omarchy.db" || -f "$REPO_DIR/omarchy.db.tar.zst" ]]
|
|
}
|
|
|
|
# Shared wording so every command explains configuration the same way.
|
|
print_no_repo_host() {
|
|
print_error "No repository host configured"
|
|
echo ""
|
|
echo "Pass --host, set OMARCHY_REPO_HOST, or write the destination to:"
|
|
echo " $BUILD_ROOT/.repo-host"
|
|
}
|