Browse documentation

Core workflow

Shares

Create expiring, revocable download links without moving the stored file.

Before you start

  • Select a workspace and project.
  • Upload the target file, or share a local path to upload it in the same step.

Create a share

expiring download link
blobyard share blobyard://demo-team/release-files/releases/report.zip --expires 7d

A share targets one object version. The raw public URL is returned once and stored only as a hash. Without --expires a share lasts seven days, and the longest allowed lifetime is thirty days.

  • Durations combine a positive whole number with d, h, m, or s, such as 7d or 45m.
  • Add --notify someone@example.com to email the link to the recipient.
  • Sharing a local path uploads it first, then shares the new version.

How recipients download

The recipient opens the share page and requests a download. Each download uses a private signed URL that lives for sixty seconds or until the share expires, whichever is sooner.

List and revoke shares

Review active shares, their use counts, and expiry on the dashboard Shares page, or list and revoke them through the API and MCP tools. Revocation blocks new download grants immediately.

Reference and troubleshooting

Syntax and behavior

Reusable syntax

share syntax
blobyard share <local-path-or-blobyard-uri> [--expires <duration>] [--notify <email>]

Concrete example

seven-day share
blobyard --workspace demo-team --project release-files share blobyard://demo-team/release-files/releases/report.zip --expires 7d

Values used

blobyard://.../report.zip
Existing remote object URI to share.
7d
Share lifetime of seven days. The maximum lifetime is thirty days.
--notify
Optional recipient email for the one-time link.

Expected result

The command returns one public share URL for the targeted version. The URL is not shown again.

If it fails

  • Use blobyard ls to correct an object URI that is not found.
  • Shorten the duration if it exceeds the thirty-day maximum.

Security and lifecycle

Raw share URLs are shown once and stored as hashes. Revocation or expiry stops new downloads without deleting the stored file.