ヘルプセンターHelp Center

dvyu preview builds Storybook, Astro, and Vite projects and creates the preview in one command. For anything else, dvyu create works with any static build directory or single HTML file, as long as it contains an HTML file.

Run dvyu lang ja or dvyu lang en. Running dvyu lang without an argument shows the current setting. It is stored in ~/.dvyu/settings.json.

Use dvyu update. It updates the latest local preview without changing its URL, so links you already shared keep working. You can pass a path like dvyu update ./dist, or an id like dvyu update <id> ./dist. Note that recreate changes the URL.

Standard previews expire 48 hours after creation, and expired previews are no longer viewable. Run dvyu list to check active previews and expiry (dvyu list all includes expired history). To share the same content again, run dvyu recreate to create a new URL. Supporters can set up to 30 days with --ttl or create permanent previews with -p.

Build static sites with relative asset paths when possible. For manual builds, use vite build --base=./. Astro can be built normally with astro build; the viewer rewrites root paths such as /_astro/.... Fully absolute URLs to external origins are left as-is and may need project-side adjustment.

Run dvyu delete <id>. You can find the id with dvyu list. To remove every preview created from this device, run dvyu delete all. Deleted previews are no longer viewable.

Uploads stop before starting if files with unsupported extensions are found. Common metadata files such as .DS_Store, .gitkeep, and Thumbs.db are ignored automatically. For other unsupported files, the CLI can exclude them after confirmation. See the docs for the full extension list.

Ciphertext files upload with a default concurrency of six. If a connection or proxy needs a different limit, set the DVYU_UPLOAD_CONCURRENCY environment variable from 1 to 16. Example: DVYU_UPLOAD_CONCURRENCY=3 dvyu create ./dist

The file or directory passed to create must contain an HTML file. index.html is preferred as the entrypoint; otherwise the first .html file is used. Check that the build output path is correct and that it produced an index.html.

Check current usage with dvyu usage and delete previews you no longer need with dvyu delete <id>. To raise the limits, supporting on Ko-fi enables 30 days of supporter benefits: 300MB storage and unlimited active previews.

The initial device registration requires a claim code created with dvyu supporter start before supporting. Include the displayed DVYU-... code in the private message for the Ko-fi payment. The code expires after 24 hours. Check the status with dvyu supporter status.

Run dvyu supporter recover and enter the email address used for Ko-fi. If it matches an unclaimed payment, you will receive a verification link valid for 15 minutes. Open it and select “Register this device” to finish; you do not need to support again. Benefits expire 30 days after the original payment, not 30 days after verification. The email address is sent to Resend for delivery, while the server stores only an HMAC hash rather than the plaintext address.

Run dvyu supporter recovery on the first device to show the recovery token, then run dvyu supporter link <recovery-token> on the second. At most two devices can be linked at once. Treat the recovery token like a password because it can link a device to the benefits.

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. A later payment never shortens an existing entitlement.

Only people who have the URL. The decryption key lives in the #k= fragment and is never sent in an HTTP request. Preview links are intended for temporary sharing with trusted recipients, so keep them private and share them only with the people who need them.

The CLI encrypts file contents and the manifest locally with AES-256-GCM before upload. 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.

Run dvyu uninstall to remove local Drovyu Preview data under ~/.dvyu. Remove the CLI itself with the package manager you installed it with, such as pnpm remove -g dvyu.