start officer-setup: pre-flight, inheriting what machine-setup already asked
The second half of the install, and a much smaller script than the original: of the old setup.sh's thirteen sections, seven are machine-setup's job now and two more were already removed. What is left is the repository, dependencies, the database, .env, the schema, the build and pm2. Pre-flight asks nothing on a normal run. machine-setup saves the account, the Officer path and the role beside itself, and this reads the same file — so machine-setup then officer-setup is two scripts and one set of answers. It prompts only where that file is absent, which is a supported case rather than an error: somebody may have provisioned the box their own way. It then checks the machine is actually ready — git, node, bun and pm2 required, docker optional — and reports all of them together with what each is for. Finding out about a missing bun three sections in, after a repository has been cloned and a database started, is a worse way to learn it. A missing required tool stops the run and names machine-setup. Found by running it: a remembered answer can go stale. My own earlier testing had left SETUP_USERNAME=gitfresh in that file, for a throwaway account I then deleted, and the run dead-ended on it. A remembered account that no longer exists is a reason to ask again, not a reason to stop — so it is checked before it is trusted, reported, and replaced. Docker being absent is a warning rather than a failure: Postgres can be one you already run, and the app store simply cannot provision until Docker is there. Sections 2 to 9 are listed and not built. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude Opus 5
+157
-16
@@ -5,26 +5,167 @@ set -e
|
||||
# officer-setup — the platform, on a machine that is already provisioned
|
||||
#
|
||||
# The second half of the install. machine-setup/ brings a blank box up to a
|
||||
# usable machine; this puts Officer on top of it: dependencies, .env, the
|
||||
# database schema, and the pm2 process list.
|
||||
# usable machine; this puts Officer on top of it.
|
||||
#
|
||||
# Run: bash scripts/setup/officer-setup.sh
|
||||
# Run as root: sudo scripts/setup/officer-setup.sh
|
||||
# =============================================================================
|
||||
|
||||
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
||||
PROGRESS_FILE="$SCRIPT_DIR/officer-setup/.setup-progress"
|
||||
|
||||
ONLY_STEP=""
|
||||
while [[ $# -gt 0 ]]; do
|
||||
case "$1" in
|
||||
--only)
|
||||
ONLY_STEP="${2:-}"
|
||||
shift 2
|
||||
;;
|
||||
--only=*)
|
||||
ONLY_STEP="${1#*=}"
|
||||
shift
|
||||
;;
|
||||
-l | --list)
|
||||
grep -oP '^step "\K[^"]+' "${BASH_SOURCE[0]}"
|
||||
exit 0
|
||||
;;
|
||||
-h | --help)
|
||||
echo "usage: officer-setup.sh [--only <step>] [--list]"
|
||||
exit 0
|
||||
;;
|
||||
*) echo "unknown option: $1" >&2 && exit 2 ;;
|
||||
esac
|
||||
done
|
||||
|
||||
# shellcheck source=officer-setup/lib/base.sh
|
||||
source "$SCRIPT_DIR/officer-setup/lib/base.sh"
|
||||
# shellcheck source=officer-setup/lib/preflight.sh
|
||||
source "$SCRIPT_DIR/officer-setup/lib/preflight.sh"
|
||||
|
||||
trap 'echo ""; echo -e "${RED}╔══════════════════════════════════════════════════╗${NC}"; echo -e "${RED}║ OFFICER SETUP FAILED${NC}"; echo -e "${RED}║ Step: ${CURRENT_STEP:-unknown}${NC}"; echo -e "${RED}║ Line: $LINENO${NC}"; echo -e "${RED}║ Command: $BASH_COMMAND${NC}"; echo -e "${RED}╚══════════════════════════════════════════════════╝${NC}"' ERR
|
||||
|
||||
# =============================================================================
|
||||
# 1. Pre-flight
|
||||
# =============================================================================
|
||||
#
|
||||
# NOT WRITTEN YET. It is being rebuilt from scripts/setup-old/setup.sh, which
|
||||
# still works and is still the one to run.
|
||||
#
|
||||
# This file exists ahead of its contents so that `bun setup` points at where the
|
||||
# installer is going rather than at a path that is about to move again. It fails
|
||||
# loudly rather than sitting empty, because an empty script exits 0 and would
|
||||
# make `bun setup` report success while doing nothing at all.
|
||||
|
||||
echo ""
|
||||
echo " officer-setup.sh is not written yet."
|
||||
echo -e "${BOLD}╔══════════════════════════════════════════════════╗${NC}"
|
||||
echo -e "${BOLD}║ Officer Setup ║${NC}"
|
||||
echo -e "${BOLD}╚══════════════════════════════════════════════════╝${NC}"
|
||||
|
||||
if [[ "$EUID" -ne 0 ]]; then
|
||||
fail "Please run as root: sudo ./officer-setup.sh"
|
||||
fi
|
||||
|
||||
# ── what machine-setup already established ──
|
||||
echo ""
|
||||
echo " It is being rebuilt from scripts/setup-old/setup.sh, which still works:"
|
||||
if load_machine_answers; then
|
||||
info "Read from machine-setup: ${MACHINE_ANSWERS}"
|
||||
else
|
||||
warn "machine-setup has not run on this machine"
|
||||
echo " That is fine if you provisioned it another way — the questions it"
|
||||
echo " would have answered are asked below instead."
|
||||
fi
|
||||
|
||||
# ── the account ──
|
||||
#
|
||||
# A remembered answer can go stale: the account it names may have been renamed or
|
||||
# removed since machine-setup ran. That is a reason to ask again, not a reason to
|
||||
# stop — so the remembered value is checked before it is trusted, and a bad one
|
||||
# is reported and replaced rather than ending the run.
|
||||
if [[ -n "$USERNAME" ]] && ! owner_exists; then
|
||||
warn "the remembered account '${USERNAME}' does not exist on this machine any more"
|
||||
USERNAME=""
|
||||
fi
|
||||
|
||||
while [[ -z "$USERNAME" ]] || ! owner_exists; do
|
||||
echo ""
|
||||
info "Which account owns this Officer install?"
|
||||
echo " Its files, its node_modules and its pm2 process list all belong to"
|
||||
echo " this account rather than to root."
|
||||
echo ""
|
||||
ask_required USERNAME "Username" "${SUDO_USER:-}"
|
||||
owner_exists || warn "There is no account called '${USERNAME}' on this machine."
|
||||
done
|
||||
|
||||
resolve_user_home
|
||||
|
||||
# ── where it goes ──
|
||||
if [[ -z "$OFFICER_ROOT" ]]; then
|
||||
echo ""
|
||||
info "Where should Officer be installed?"
|
||||
echo " One directory holding the app, its data, the item store and any"
|
||||
echo " containers the app store provisions."
|
||||
echo ""
|
||||
ask_required OFFICER_ROOT "Path" "${USER_HOME}/officerdev"
|
||||
fi
|
||||
OFFICER_ROOT="${OFFICER_ROOT/#\~/$USER_HOME}"
|
||||
[[ "$OFFICER_ROOT" == /* ]] || fail "That needs to be an absolute path — got '${OFFICER_ROOT}'"
|
||||
OFFICER_ROOT="${OFFICER_ROOT%/}"
|
||||
|
||||
info "Account: ${USERNAME} (home ${USER_HOME})"
|
||||
info "Officer: ${OFFICER_ROOT}"
|
||||
[[ -n "$MACHINE_ROLE" ]] && info "Role: ${MACHINE_ROLE}"
|
||||
|
||||
# ── is the machine actually ready ──
|
||||
#
|
||||
# Checked and reported together. Finding out about a missing bun three sections
|
||||
# in, after a repository has been cloned and a database started, is a worse way
|
||||
# to learn it.
|
||||
echo ""
|
||||
echo " bash scripts/setup-old/setup.sh # full install"
|
||||
echo " OFFICER_PROFILE=light bash scripts/setup-old/setup.sh # light install"
|
||||
info "What Officer needs from this machine"
|
||||
|
||||
mapfile -t MISSING < <(missing_tools)
|
||||
mapfile -t MISSING_OPT < <(missing_optional_tools)
|
||||
|
||||
for t in "${REQUIRED_TOOLS[@]}"; do
|
||||
if command -v "$t" &>/dev/null; then
|
||||
printf ' %-6s %-10s %s\n' "$t" "ok" "$(tool_why "$t")"
|
||||
else
|
||||
printf ' %-6s %-10s %s\n' "$t" "MISSING" "$(tool_why "$t")"
|
||||
fi
|
||||
done
|
||||
for t in "${OPTIONAL_TOOLS[@]}"; do
|
||||
if command -v "$t" &>/dev/null; then
|
||||
printf ' %-6s %-10s %s\n' "$t" "ok" "$(tool_why "$t")"
|
||||
else
|
||||
printf ' %-6s %-10s %s\n' "$t" "absent" "$(tool_why "$t") — optional"
|
||||
fi
|
||||
done
|
||||
|
||||
if ((${#MISSING[@]} > 0)); then
|
||||
echo ""
|
||||
fail "Missing: ${MISSING[*]}. Run scripts/setup/machine-setup/machine-setup.sh first, or install them yourself."
|
||||
fi
|
||||
|
||||
if ((${#MISSING_OPT[@]} > 0)); then
|
||||
echo ""
|
||||
warn "No Docker. Postgres will have to be one you already run, and the app"
|
||||
echo " store cannot provision anything until Docker is installed."
|
||||
fi
|
||||
|
||||
if [[ -f "$PROGRESS_FILE" ]]; then
|
||||
echo ""
|
||||
info "Resuming — $(wc -l <"$PROGRESS_FILE") step(s) already done, and they will be skipped"
|
||||
echo " To start over instead: sudo rm ${PROGRESS_FILE}"
|
||||
else
|
||||
echo ""
|
||||
echo " This can be stopped at any point and run again later. Completed"
|
||||
echo " steps are remembered and skipped."
|
||||
fi
|
||||
|
||||
# =============================================================================
|
||||
# NOT BUILT YET
|
||||
# =============================================================================
|
||||
#
|
||||
# 2 Repository clone or locate the platform at $OFFICER_ROOT/platform
|
||||
# 3 Dependencies bun install
|
||||
# 4 Database Postgres in docker, or one you already run
|
||||
# 5 Environment .env
|
||||
# 6 Schema db:push
|
||||
# 7 Build gen:index
|
||||
# 8 Services pm2 startOrRestart · save · startup
|
||||
# 9 Verify are the processes actually up
|
||||
|
||||
echo ""
|
||||
echo -e "${BOLD} Pre-flight complete.${NC} The remaining sections are not built yet."
|
||||
echo ""
|
||||
exit 1
|
||||
|
||||
Reference in New Issue
Block a user