v1.2.5

The commands do the work, wherever the files are

A compose installation keeps its token file, its uploads and its telemetry
marker in a volume this machine cannot open. The answer to that used to be a
docker command to copy, which is not an answer: you asked GoDrop to make a
token.

token create, token list and token revoke now run where the file is, in
the running container or a throwaway one when the service is stopped, using the
same binary the service runs. The output is the one a local installation
prints, --json included.

$ godrop token create --name claude-code

Token created

  ┌─────────────────────────────────────┐
  │ gd_e92b1706682a8625484b3e4b7ac54567 │
  └─────────────────────────────────────┘

  ✓ name: claude-code (usable immediately, no restart needed)

godrop telemetry off reaches the one that would send

It wrote its marker beside this shell and reported that nothing more would be
sent, while the container carried on sending: the marker it reads is in the
volume. It is written there now, and telemetry status asks the container,
which is the copy that knows.

godrop doctor asks the container about the container

The storage, the permissions and the token file are inside it; the network and
the reachability are out here. Both are checked and one report comes out,
rather than a command to run for the other half.

godrop uninstall takes the service with it

It left the container running and the uploads on a volume it never mentioned.
It now stops the service and removes the container and its network, and with
--purge the volume as well, before deleting the configuration that says where
they are.

Also

godrop health probes the port the installation listens on rather than the
default one.

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

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