← Bosun

Installing

Launchpad PPA (recommended) or the standalone .deb package — install order, verifying the install, and the standalone-mode fallback with no argus-tty.

Install order matters: argus-tty first (developer/admin accounts, the sudoers whitelist, the webapps/rvm groups), then bosun on top.

Option A — Launchpad PPA (recommended)

sudo add-apt-repository ppa:yadavramlaxman/argus-tty
  sudo add-apt-repository ppa:yadavramlaxman/bosun
  sudo apt update
  sudo apt install argus-tty bosun

Upgrades arrive via your regular apt upgrade instead of re-downloading a .deb by hand. See argus-tty/PACKAGING.md if you want to build and publish your own PPA instead of using these.

Option B — the .deb package

sudo apt install ./argus-tty_1.0.0_all.deb
  sudo apt install ./bosun_1.0.0_all.deb

Verify both landed correctly before provisioning any app:

sudo argus-tty status   # confirm green
  bosun version           # confirms `bosun` resolves its own helper scripts at all —
                           # failing here means the .deb didn't lay files down where
                           # `bosun` expects them to be

bosun's own scripts (add.sh, install, setup, do-release, release-cleanup, bootstrap) source argus-tty's installed /usr/lib/argus-tty/lib/common.sh directly for the constants/helpers they need (AT_WEBAPPS_ROOT, AT_WEBAPPS_GROUP, AT_RVM_ROOT, AT_WEBAPPS_SVC_USER, require_root, valid_username, info/warn/ error) — a real cross-package dependency, not just a doc note.

No argus-tty? Bosun falls back to a single-operator standalone mode instead of refusing to run — no tiers, no separate service account, every secret only as isolated as your one account's own permissions. This also works the other way: sudo bosun mode standalone/argus-tty lets you choose explicitly regardless of what's installed — force standalone on a box that happens to have argus-tty too, or require argus-tty strictly so bosun errors instead of silently degrading if it's ever removed by accident. Switching modes never touches an existing app's code or shared/.env content — see standalone mode for the full tradeoff and the exact bosun add/bosun restart steps to apply a mode switch to apps already deployed.

Every developer, admin, and deployer account (managed by argus-tty) is automatically a member of a shared webapps group (and of rvm, if RVM is already installed on the box) — see argus-tty's add-developer.sh. This is what lets them create and edit application files without any sudo access, on top of argus-tty's existing whitelist model.