How marcjwrigg/armoryhub-selfhost-install works
ArmoryHub self-host install is a configuration-and-operations repository; the application itself runs from a container image. The principal workflow is an administrator running the installer, which prepares the Compose deployment and starts the app, database, backups, and optional network access. The README also documents a Debian/Ubuntu bootstrap path, a Caddy/reverse-proxy setup, and ongoing server management. Relationships reflect the README only; source excerpts were unavailable, so uncertain implementation details are omitted.
Main entry points: docker-compose.yml Compose deployment · install.sh Installer · bootstrap-debian.sh Debian bootstrap · armoryhub ArmoryHub CLI
Components 15
Installation
- Installer
install.sh - Debian bootstrap
bootstrap-debian.sh
Runtime stack
- Compose deployment
docker-compose.yml - Environment settings
env.example - Postgres
docker-compose.yml - ArmoryHub app
docker-compose.yml - Nightly backups
docker-compose.yml - Tailscale access
docker-compose.yml - Caddy profile
docker-compose.yml
Server operations
- ArmoryHub CLI
armoryhub
Other components
- Administrator
- Docker Engine
- User browser
- Reverse proxy
- Hosted ArmoryHub
Connections 16
- Administrator → Installer: runs
- Installer → Compose deployment: prepares
- Installer → Environment settings: generates
- Administrator → Debian bootstrap: runs
- Debian bootstrap → Docker Engine: installs
- Compose deployment → Docker Engine: starts services
- Compose deployment → Postgres: configures
- Compose deployment → ArmoryHub app: configures
- Compose deployment → Nightly backups: configures
- Compose deployment → Tailscale access: configures
- Compose deployment → Caddy profile: offers profile
- User browser → ArmoryHub app: accesses
- Administrator → ArmoryHub CLI: runs commands
- ArmoryHub CLI → Docker Engine: manages deployment
- Reverse proxy → ArmoryHub app: forwards traffic
- Hosted ArmoryHub → ArmoryHub app: account migration