seawall proxy migrate
Move the way in from Nginx Proxy Manager to Traefik.
Move the way in from Nginx Proxy Manager to Traefik
Reads NPM's database read-only: every proxy host, redirect, 404 host and stream, their certificates (Cloudflare origin ones too) and access lists, and says what each becomes in Traefik and what can't come. With --yes: NPM's database is backed up, Traefik is started beside NPM with no host port, every domain is fetched through each and must answer the same, then NPM stops (its data kept), Traefik takes 80 and 443, and every domain is checked again. A failure puts NPM back.
Usage
seawall proxy migrate [OPTIONS] --to <TO>
Changes the host
Without --yes it prints the plan and changes nothing.
Options
--to <TO>The proxy to move to
--printPrint each file Traefik would read (certificates by path, never their keys)
--yesCarry out the move (the NPM stack's name is typed)
--confirm <STACK>The NPM stack's name, for a move without a terminal
--resumeCarry on an unfinished move from where it stopped
--rollbackUndo an unfinished move: Traefik stopped, NPM started again
--certsAfter the move: hand the hosts still on NPM's Let's Encrypt certificates to Traefik's own resolver
--cleanA week after the move: remove NPM's stopped stack from its manager (its data folders and volumes kept, its compose backed up)
--waitAfter a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (
SeawallDeployWorse)
Examples
seawall proxy migrate --to traefik
seawall proxy migrate --to traefik --print
seawall proxy migrate --to traefik --yes
seawall proxy migrate --to traefik --rollback --yes