seawall stack expose

Put a web app that publishes host ports behind the proxy.

Put a web app that publishes host ports behind the proxy

Its service joins the ingress network and stops publishing, and the proxy routes the domain to it (NPM, Traefik or Caddy). A port that isn't its web port is dropped only when named; the stack is rolled back if it doesn't come up.

Usage

seawall stack expose [OPTIONS] <STACK> <SERVICE> <DOMAIN>

Changes the host

Without --yes it prints the plan and changes nothing.

Arguments

<STACK>

The stack, by Portainer name or directory

Required.

<SERVICE>

The service in its compose file

Required.

<DOMAIN>

The domain it answers on

Required.

Options

--port <PORT>

Its web port inside the container (default: the one TCP port it publishes)

--drop-port <HOST_PORT>

Another host port it publishes, to drop with the rest (repeat for each)

--allow <CIDR>

Let only these addresses in, through an NPM access list (comma-separated IPs or CIDRs); needed for anything root on this host

--yes

Carry out the plan (without it, this is a dry run)

--wait

After a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (SeawallDeployWorse)

Every command also takes the global options.

Examples

seawall stack expose blog web blog.example.org
seawall stack expose vault vaultwarden vault.example.org --port 80 --drop-port 3012 --yes