ドキュメントDocumentation

Drovyu Preview CLI creates temporary preview links for static builds. It is useful when you want to share a Vite, React, or Storybook static build without deploying it as a permanent site.

The CLI encrypts every file and its manifest locally before upload. The AES key is kept in the #k= URL fragment and is never sent in an HTTP request.

The “Try in browser” action creates one static preview without installing the CLI. Select an index.html file, a static output folder, or a ZIP, then review the selection and limits before creating it. No file is sent before confirmation.

File contents, names, paths, MIME types, and the entrypoint are encrypted in the browser. Only each file extension is sent in plaintext so the server can reject prohibited formats.

• Up to 10 MiB and 100 files
• An HTML file is required; only the CLI allowlist is accepted
• Expires 24 hours after creation
• One active trial preview per browser
• No update, extension, or manual deletion

Requirements:

• Node.js 20 or later
• A static build directory such as Vite dist or Storybook static output

Install the npm package with pnpm or npm.

One-off execution also works:

For a Storybook, Astro, or Vite project, one command builds the project and creates the preview.

If you already have a build directory, use create. When no path is provided, it uses dist if it exists, otherwise index.html if it exists.

Send the printed URL. The decryption key lives in the #k= fragment, and the preview expires after 48 hours.

Builders supported by dvyu preview:

• Storybook (default output: storybook-static)
• Astro (default output: dist)
• Vite (default output: dist)

Vite is built with a relative base and the selected output directory. Astro is built normally because its base option is a deployment pathname; the Drovyu viewer resolves Astro's root asset paths. Use --out-dir when your project uses a different output directory.

Uploads stop before starting if unsupported files are found. Common metadata files such as .DS_Store, .gitkeep, and Thumbs.db are ignored automatically. If other unsupported files are found, the CLI can exclude them after confirmation.

Supported extensions:

If index.html exists at the upload root, it is used as the preview entrypoint. Ciphertext files upload with a default concurrency of six after encryption finishes. Set DVYU_UPLOAD_CONCURRENCY from 1 to 16 when a connection or proxy needs a different limit.

For the most reliable previews, build static sites with relative asset paths. Astro and some other builders emit root paths such as /_astro/.... The Drovyu Preview viewer rewrites those paths, including nested pages, but fully absolute URLs to external origins are left as-is.

If you build manually before running dvyu create, prefer:

Supporter benefits are normally active for 30 days after each Ko-fi support, any amount. A later payment never shortens an existing entitlement.

Activation flow: before supporting, run dvyu supporter start on the first device and include the displayed DVYU-... code in the private message for the Ko-fi payment. A claim code expires after 24 hours, and the initial device registration requires a code created before supporting. Check the status with dvyu supporter status.

If you forgot the code, run dvyu supporter recover instead of supporting again. When the Ko-fi email address matches an unclaimed payment, a verification link valid for 15 minutes is sent. Benefits expire 30 days after the original payment. The email address is sent to Resend for delivery, while the server stores an HMAC hash rather than the plaintext address.

After the supporter period ends, new previews cannot use -p or --ttl. Existing permanent previews are not deleted immediately, but access no longer extends their expiry and they remain available only until the currently scheduled deletion time.

The CLI encrypts every file and its manifest locally with AES-256-GCM before upload. The AES key is kept in the #k= URL fragment and is never sent in an HTTP request. The server does not receive original file contents, filenames, MIME types, the entrypoint, or the AES key. Operational metadata remains unencrypted, including the preview and device ids, aggregate sizes, file count, creation and access times, expiry, and retention mode. See docs/ENCRYPTION.md for the encryption design and executable verification.

Notes:

• Preview links are intended for temporary sharing with trusted recipients.
• Drovyu Preview is not a full security sandbox.
• The Viewer JavaScript and delivery infrastructure are part of the trust boundary. The service does not claim active-server zero knowledge.
• Do not use the service for confidential, NDA, or personal data, private keys, or credentials.
• The viewer rewrites same-origin asset links for encrypted previews, but unusual runtime routing or external absolute assets may still need project-side adjustment.
• Keep generated preview links private.
• Supporter credentials are stored in ~/.dvyu/support.json. It contains the device and recovery tokens, so never share it or commit it to a repository.

Compare gitHead with the corresponding GitHub Release commit. See Security for encryption details and Trust for assurance scope and trust boundaries.

Removes local Drovyu Preview data (previews.json, settings.json, device.json, and support.json under ~/.dvyu).

Remove the CLI itself with the package manager you installed it with.