dropbin 1.1.0

db — upload a file, get a pin; give the pin back, get the file. Two
operations, no listing, no dependencies, Node 18 or newer.

Install

curl -fsSL https://files.dharun.dev/install.sh | sh   # macOS, Linux, WSL
npm i -g dropbin                                      # anywhere npm is

irm https://files.dharun.dev/install.ps1 | iex        # Windows

Then db for the menu, or db up ./file, db get 4821, db qr 4821,
db free. db --help lists the rest.

The installers fetch this release, unpack it into ~/.local/share/dropbin
(%LOCALAPPDATA%\dropbin\app on Windows) and put db on your PATH. Fetched
from a deployment rather than from GitHub, they also point the installed db
at that deployment — DROP_HOST still overrides it. Nothing is stored: the
password is asked for on every run.

--version 1.1.0 pins a release, --dir / --bin move where things land,
--tarball / -Archive install one of the files below directly, and
--uninstall / -Uninstall removes everything again. On Windows those go
through a script block, since iex cannot pass arguments:

& ([scriptblock]::Create((irm https://files.dharun.dev/install.ps1))) -Uninstall

A machine with no Node at all wants curl -s https://files.dharun.dev/cli -o drop && bash drop instead, which needs nothing.

Files

Both hold the same package.

file	for
dropbin.tgz	install.sh, and npm i -g ./dropbin.tgz
dropbin.zip	install.ps1, which unpacks with Expand-Archive

The names carry no version, so
https://github.com/dharunashokkumar/dropbin/releases/latest/download/dropbin.tgz
always resolves to the newest one.