Maintainer overview & fork model

Entry point for changing BOA itself. Two things live here: the stack architecture as a code reader sees it — entry scripts, sourced library sets, the deployable payload — and the fork model: every component is an omega8cc repository, omega8cc is upstream, and nothing defers to pre-fork projects.

The one-paragraph map, verified at source: BOA.sh.txt is the meta installer; it exports the release identity (_tRee, _xSrl, _rLsn, _bTs — BOA.sh.txt:47-50), deploys serial-gated tools through _fetch_versioned <dest> <url> fNN (BOA.sh.txt:1056), and hands off to BARRACUDA.sh.txt (system/stack installer) and OCTOPUS.sh.txt (per-instance platform layer). Each entry script sources lib/settings/{barracuda,octopus}.sh.cnf — defaults plus the bootstrap helpers: _download_helpers_libs (barracuda.sh.cnf:1613) fetches the BOA payload into ${_bldPth} — _download_boa_code tarball in the default BATCH _DL_MODE, or a git clone --branch ${_BRANCH_BOA} when _DL_MODE=GIT (barracuda.sh.cnf:1636) — then its own include list from lib/functions/: BARRACUDA loads helper dns system sql valkey redis nginx php solr master xtra firewall hotfix (BARRACUDA.sh.txt:275), OCTOPUS loads helper dns satellite (OCTOPUS.sh.txt:266). master.sh.inc and satellite.sh.inc are deliberately parallel, never co-loaded — compare master.sh.inc:576 with satellite.sh.inc:3155; a fix that touches one side is patched into the other as a separate copy, never DRYed into a shared function. The Aegir layer is four omega8cc forks — Hostmaster (frontend distro), Hosting (hosting_* modules), Provision (Drush-based backend), and a patched classic Drush 8 — all fetched from _gitHub="https://github.com/omega8cc" (BARRACUDA.sh.txt:183): hostmaster and hosting at branch 5.x-${_tRee} (master.sh.inc:576-577), provision at ${_BRANCH_PRN} (master.sh.inc:688), Drush 8 as a version-pinned tarball (master.sh.inc:735; pins at BARRACUDA.sh.txt:48-51).

Pages in this topic

  • Stack architecture — the code-reader's map: the BOA.sh.txt → BARRACUDA.sh.txt / OCTOPUS.sh.txt entry chain, the lib/functions/*.sh.inc include sets, the aegir/ payload (conf/, tools/, scripts/ with AegirSetup{A,B,C,M}.sh.txt), and where each file lands on a deployed box.
  • The omega8cc fork model — the four Aegir-layer forks and the BOA repo itself, why omega8cc is the upstream of record, the public branch families (5.x-dev/-base/-edge, 5.x-pro*, 5.x-lts*), and which branch or pin each component installs from.

Release mechanics — how a tag on 5.x-pro/5.x-lts reaches every production box through the SKYNET self-update agent (_SKYNET_MODE gate, aegir/tools/system/owl.sh:349, deployed as /var/xdrago/owl.sh) and how the fNN serials force tool re-fetch — are the Release model & SKYNET pipeline topic, indexed from the guide front page.

Reference

  • Variables and Commands — consolidated _VAR and CLI tables cited throughout this guide.
  • Discontinued features — components that left the stack; check before documenting anything you find only in old trees.