https:// address, you are signed in as its admin, and you know how to back it up,
upgrade it and go back. Run a team server explains the settings and the
image.
Run it
Run the image with a named volume. The port is published on127.0.0.1 only, so the
plain HTTP server is reachable from this machine and nowhere else:
aboard.example.com on the same machine, in front of
127.0.0.1:7400, keeping the Host header and allowing 11-minute reads: the event
stream and long waits for messages stay open for up to 10 minutes. Never publish port
7400 on every interface (-p 7400:7400); if the proxy runs elsewhere, the port must sit
only on a private network the proxy reaches. Check the server answers for its host:
"mode":"team". With any other Host, it is 421.
Sign in as the first admin
Pipe the key intoaboard login on your own machine, and delete the file once the login
worked:
Back up
docker stop returns once the container has exited. The copy holds every key and
message, so it goes in a new folder only you can read: mkdir refuses a name that
already exists, a link included, and inside the container umask 077 keeps the file
private and set -C refuses to write over anything. Then start the server again:
Upgrade, and go back
Read the release notes, then stop and remove the container, and run the samedocker run as in Run it with the new tag; the volume keeps the data.
To go back after an upgrade that worked, put the copy the upgrade made in place of the
database:
docker run from Run it with the older tag. Anything written
after that copy was made is lost.