v1.2.6

Changing a setting is the same command with the setting on it

godrop init --base-url https://files.example.com on a machine that was
already set up printed an update nobody asked for and dropped the flag on the
floor. A setting named on the command line is an instruction to change it:

$ godrop init --base-url https://files.example.com
  ✓ GoDrop is already set up in /home/you/.godrop

Changing
  ✓ base url               https://files.example.com

Updating
  ✓ the container is running the newest image

The value is checked before anything is written, the .env keeps its token,
its comments and every line you did not mention, and the service restarts into
the change. --port reaches the compose file that publishes it, and the volume
that file names is read back out of it first, so an installation keeping its
uploads on the host is not moved onto a fresh empty one.

--base-url, --port, --max-file-size, --max-total-size, --retention,
--tls, --tls-cert, --tls-key and --telemetry all work this way.
--force still means "set it up again from scratch".

Also

The closing summary asks for a token with godrop token create, which reaches
the file wherever it is, rather than with a docker command; and the diagnosis
reports the round trip once rather than from both sides of the container.

Install

curl -fsSL https://godrop.sh/install.sh | sh

Or with Docker:

docker run -d --name godrop --restart always -p 8747:8747 \
  -e GODROP_TOKENS=$(openssl rand -hex 16) \
  -v godrop-data:/data ghcr.io/fatihbaltaci/godrop:v1.2.6

Debian and RPM packages are attached below; they set up the systemd service
for you. Every archive's checksum is listed in SHA256SUMS.