Adds a manifest-driven "Install CircuitForge Apps" menu to install.sh, alongside the existing extras-menu pattern. - cf-apps/*.manifest: one file per product (circuitforge-core, peregrine, kiwi, snipe, turnstone, pagepiper, linnet - the beta/alpha menagerie products), declaring repo URLs, supported install types, conda env, .env template, and per-install-type setup hooks. Hooks prefer shelling out to each product's own install.sh/Makefile/docker-compose rather than reimplementing their setup logic. - lib/cf-apps.functions: registry loader, provisioning-profile prompt (oem/collaborator/orchard), app multiselect menu, and the install dispatcher (clone, .env bootstrap, install-type selection, hook dispatch). circuitforge-core installs automatically as a dependency for apps that declare app_needs_core=true. Provisioning profiles gate both which apps are offered and which remote credentials are used: - oem: public CircuitForgeLLC GitHub mirrors only, no Forgejo access, no circuitforge-orch (product install menu only) - collaborator: private Circuit-Forge Forgejo, same product menu - orchard: narrow flow, not the product menu - clones circuitforge-orch (Forgejo-only, no public mirror exists) and hands off interactively to its own install.sh, which gathers agent/coordinator topology itself (it has no --topology/--coordinator-url flags to script around). NOTE: circuitforge-orch has no model-sync/cache-sync mechanism today (checked its install.sh and README); this wrapper doesn't invent one. Design rationale and survey of each product's real install story: circuitforge-plans/cf-node-bootstrap/superpowers/plans/2026-07-17-cf-apps-install-menu.md
29 lines
1,010 B
Text
29 lines
1,010 B
Text
app_name="peregrine"
|
|
app_desc="LLM-powered job discovery and application pipeline (beta)"
|
|
app_repo_url_github="https://github.com/CircuitForgeLLC/peregrine.git"
|
|
app_repo_url_forgejo="https://git.opensourcesolarpunk.com/Circuit-Forge/peregrine.git"
|
|
app_available_profiles=(oem collaborator)
|
|
app_install_types=(bare-metal docker podman)
|
|
app_conda_env="cf"
|
|
app_env_template=".env.example"
|
|
app_needs_core=true
|
|
|
|
# peregrine ships its own install.sh (installs Docker/Podman + NVIDIA
|
|
# toolkit per-distro) and a Makefile (setup -> preflight -> start, with
|
|
# PROFILE=remote|cpu|single-gpu|dual-gpu). Shell out rather than
|
|
# reimplementing that logic here.
|
|
app_setup_bare_metal() {
|
|
local dir="$1"
|
|
boxline "Handing off to ${app_name}'s own install.sh..."
|
|
(cd "$dir" && ./install.sh)
|
|
}
|
|
|
|
app_setup_docker() {
|
|
local dir="$1"
|
|
boxline "Handing off to ${app_name}'s own install.sh (choose a docker/podman GPU profile when prompted)..."
|
|
(cd "$dir" && ./install.sh)
|
|
}
|
|
|
|
app_setup_podman() {
|
|
app_setup_docker "$1"
|
|
}
|