v1.2.3

Installing needs no root

The installer used sudo to reach /usr/local/bin. It does not any more: the
binary goes to ~/.local/bin, the configuration to ~/.godrop and the uploads
into a docker volume, so updating and removing GoDrop later are the work of the
same account. Root is used when you are already root, or when you name the
destination yourself with GODROP_BIN_DIR, and never behind your back.

The one privilege this does need, once, is membership of the docker group.
The checks now ask the daemon rather than only the plugin, before anything is
written:

✓ docker compose         available
⚠ docker                 the docker daemon does not answer this user
    → start it, or join the group once: sudo usermod -aG docker $USER  (then log out and back in)

godrop update says what it needs

Updating a binary in /usr/local/bin as an ordinary user failed with
"permission denied" on a temporary file nobody had heard of, after downloading
the whole archive. The directory is checked first now, and the message is the
command that gets past it:

error: /usr/local/bin is not writable by this user, so the binary cannot be replaced.

  Try:  sudo godrop update

sudo changes where the installation is, too: root's own configuration directory
is empty, and the compose service that needs updating belongs to whoever ran
setup. Every command that looks for an installation now follows SUDO_USER
home when root has none of its own.

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.3

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