Story
As a Linux operator managing a CD target host, I want to install the Fallout deployment agent with apt install fallout-agent from a Fallout-hosted APT repository so I get a systemd-managed daemon that survives reboots and updates via apt upgrade, without resorting to curl-bash installers.
Why
RFC #113 defines fallout-agent as a self-contained executable that operators run on hosts the forge runner can't reach. For Debian-family Linux hosts (Debian, Ubuntu, and downstreams — by far the dominant server distros), .deb + an APT repo is the expected install path. Curl-piped installers and bare tarballs both fail policy in serious shops; a signed APT source is the baseline.
Acceptance criteria
Sub-tasks (filled in after creation):
Out of scope
- RPM / Fedora / RHEL packaging — separate story when there's pull from that ecosystem.
- Snap / Flatpak — orthogonal distribution channels; revisit later.
- Pre-release /
unstable suite — only stable channel for now.
Related
Story
As a Linux operator managing a CD target host, I want to install the Fallout deployment agent with
apt install fallout-agentfrom a Fallout-hosted APT repository so I get a systemd-managed daemon that survives reboots and updates viaapt upgrade, without resorting to curl-bash installers.Why
RFC #113 defines
fallout-agentas a self-contained executable that operators run on hosts the forge runner can't reach. For Debian-family Linux hosts (Debian, Ubuntu, and downstreams — by far the dominant server distros),.deb+ an APT repo is the expected install path. Curl-piped installers and bare tarballs both fail policy in serious shops; a signed APT source is the baseline.Acceptance criteria
Sub-tasks (filled in after creation):
.debfor amd64 and arm64 (Debian 12 / Ubuntu 22.04 / 24.04 baselines).deb.debon stable tag + add Linux smoke testOut of scope
unstablesuite — only stable channel for now.Related