alerts and silence
Lists firing Grafana alerts. alerts <name> reads what fired it live (a listener's PID and command line, a container's last log lines and restart count, the CVEs an update fixes) and lists the seawall command that resolves it, if there is one. silence adds a Grafana silence. sev0 alerts can't be silenced.
db backup
Dumps each MySQL, MariaDB and Postgres database with the client inside its own container. Each dump is restored into a throwaway container with no network. Its table count per schema is compared with the live database. The nightly timer keeps 14 dumps and raises an alert when a dump or restore test fails.
game up
Starts and stops game server stacks. On a port clash it moves the new game to the next free port and prints the port players connect to. The running game is left alone. game down silences the game's alerts before it stops. The game's ports are added to and removed from the port allowlist.
host
Graphs CPU, memory, disk and network from Prometheus, from the last hour up to 30 days with --since. Memory is split by stack, the Docker engine, system services, login sessions and page cache, from cgroup v2. It also shows the running and newest kernel, a pending reboot, RAID state and disk use. host mem ranks stacks by memory growth over the last day.
images
Checks each running container's registry daily for a newer release in its major and for new majors. Trivy runs in a digest-pinned, locked-down container. It scans the running image and the candidate and counts the Critical and High CVEs the update fixes. A local build is checked against its base image. images ls lists the results. images explain <container> lists the CVEs by package. It never changes a stack. stack update takes the update.
init
Sets up a new Ubuntu or Debian server, or links in with an existing one. Docker and Compose must be installed first. It adds Portainer or Compose, a reverse proxy (Nginx Proxy Manager, Traefik or Caddy), Prometheus, Grafana, cAdvisor, node-exporter, Loki, Alloy, CrowdSec, auditd, ufw rules and unattended security upgrades. Every image is pinned by digest. Each step is checked first and skipped if it's already in place. On a terminal it shows the plan and asks Carry out these steps? [y/N]. Off a terminal it prints the plan and takes no action. It ends with the ssh -L line and the login for each web UI.
new
A wizard for a new app, internal service or game server. It searches Docker Hub with the words as typed, hyphenated and joined, and flags look-alikes and images with few pulls. It reads the image's user, ports and volumes from the registry and its README. The compose file runs as a non-root user with capabilities dropped and a memory limit, and passes the lint. A non-root app's volumes are created and handed to its user before the first start.
proxy hosts and proxy certs
proxy hosts reads every route from Nginx Proxy Manager (its database), Traefik (labels and file provider) or Caddy (its admin API). It flags routes without HTTPS, without an HTTP redirect or with a backend off the proxy network. proxy certs asks the proxy for each certificate it serves, so Cloudflare origin certificates show too. proxy certs install installs a Cloudflare origin certificate you paste in. It checks the key matches, switches every site the certificate names and confirms what the proxy serves.
stack lint and stack harden
stack lint checks each compose file against 32 hardening rules. They include no-new-privileges, cap_drop: [ALL], memory and PID limits, pinned images, no Docker socket, no host root mount, databases off the proxy network and no relative bind mounts under Portainer. A deploy that adds an error is refused. A finding is accepted on purpose with a # seawall-lint: allow comment and an optional expiry date. stack harden writes the missing settings, with memory limits at twice the 14-day peak from Prometheus.
stack migrate
Moves a running stack between Portainer and Compose under the same project name, so its volumes carry over. The stack's env moves with it, into a 0600 .env for Compose. It backs up the deployed compose first. If the stack doesn't come back healthy, it's moved back. It runs only after you type the stack's name.
stack update
Bumps an image tag from the daily check, or to --to TAG, and redeploys through Portainer or Compose with the stack's env sent back unchanged. It backs up the deployed compose and pulls only the images it changes. It waits for every container to be running and healthy. If one doesn't settle, it offers stack rollback. Majors need --major. A database major also needs a restore-tested dump from the last 24 hours and the stack's name typed. Afterwards the update check runs again, so its alerts clear.
status
One screen of what needs attention. Firing alerts and active silences, stacks that are stopped, restarting or drifted from their deployed compose, unexpected published ports, pending image updates with the CVEs they fix, apt updates, database backup age, the config repo and collector health. --brief prints one line for the SSH login banner. --json is for scripts. --check exits 1 when something needs attention.