seawall stack deploy
Deploy the disk compose, keeping the stack's env (backs up first).
Usage
seawall stack deploy [OPTIONS] <STACK>
Changes the host
Without --yes it prints the plan and changes nothing.
Arguments
<STACK>The stack, by Portainer name or directory
Options
--compose <COMPOSE>Compose file (default: the stack's directory under ~/docker)
--set-env <NAME>Set or add an env var, taking its value from this shell's environment
--pulldocker pull the stack's images first (needed for a same-tag rebuild)
--allow-lint-errorsDeploy even if the change adds hardening errors (see
seawall stack lint)--startStart a stopped stack (without it, a stopped stack is updated and stays offline)
--rollback-on-failureIf the stack doesn't come up healthy, roll back without asking
--accept-grantsAccept the root grants it starts, writing each one's
# seawall-lint: allowline, so later starts confirm with Enter--data-backed-upEach database has a tested backup of yours: no restore-tested dump from the last 24h needed
--yesCarry out the plan (without it, this is a dry run)
--confirm <NAME>The stack's name, to start one handed the host's root without a terminal (
--yesalone asks for it to be typed)--waitAfter a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (
SeawallDeployWorse)
Examples
seawall stack deploy nextcloud
seawall stack deploy nextcloud --pull --yes