v1.2.1

godrop doctor finds your installation

Run from a shell, doctor read only the environment, which is not the service's:
it reported no tokens, the wrong data directory and a 401 on the round trip. It
now reads the .env setup wrote. A compose deployment keeps its files in a
volume nothing outside the container can see, so that one is checked over HTTP
and the command for the rest is printed with the report.

The installer lands on your PATH

~/.local/bin is added to the PATH at login, and only if it already exists, so
a binary installed there was invisible to the shell that installed it. The
installer now prefers /usr/local/bin, and when it cannot, it adds the line to
your shell profile and prints the one to run now.

Setup ends with where everything is

Your installation
  - location             /home/you/.godrop
  - service              docker compose, container godrop-godrop-1
  - uploads              docker volume godrop_godrop-data
  - address              http://localhost:8747

Use it
      curl -X POST -H "Authorization: Bearer gd_..." -F "file=@/home/you/.godrop/sample.png" ...

  A token of its own for an agent, a script or a second machine:
      docker compose --project-directory /home/you/.godrop run --rm godrop token create --name claude-code

Also: /data in the image is 0700, which a fresh named volume inherits, and
godrop token create prints the address this instance actually answers on.

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

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