squarecloud blob manages the files in your Blob Storage. A file is identified by its ID, which blob list and blob upload print.
The commands need an API key with the blob:read and blob:write scopes. The browser login asks for both. A key from a browser login before version 3.2.0 lacks them: the first Blob command then asks you to run squarecloud auth login again. A key in SQUARECLOUD_API_KEY needs both scopes too.
squarecloud blob list
Usage
prefix. A private file shows (private) instead of a URL.
--json, it prints the files as a JSON array.
squarecloud blob upload
Usage
Uploads one file and prints its ID and URL. The service keeps the extension of the file. In the default name, characters the service doesn’t accept are replaced with
_. To send a folder, zip it first with squarecloud zip.
Output
- Large files: a file above 90 MiB goes up in parts, six at a time, sized from the limits the service sends. The progress goes to stderr, so stdout carries only the result.
- Failures: a failed or canceled (
Ctrl+C) upload is aborted, so it doesn’t hold one of your open upload slots. Only reads and parts are retried, never a rate limit. - Private files: instead of a URL, the CLI shows the command that makes a temporary link,
blob url.
--json, stdout carries only the stored file (ID, visibility, URL and size, plus the number of parts for an upload in parts) as JSON.
squarecloud blob url
Usage
$(...). For a temporary link, the CLI says on stderr until when it is valid.
--json, it prints the link with its expiry, visibility, size and content type.
squarecloud blob delete
Usage
Asks
Delete <ID> for good? There is no trash [y/N] before deleting. delete has no JSON output.
squarecloud blob stats
Usage
Output
--json, it prints your full usage record as JSON.
Related
To use Blob Storage from your own code, start with the Blob SDK.

