FAQ
Common questions about the CLI.
Updated
On this page
Do I need to configure DigitalOcean or my own bucket?
No. The Dash4Devs backend owns the bucket. You never see or store credentials.
Common questions about the CLI.
Updated
No. The Dash4Devs backend owns the bucket. You never see or store credentials.
Only .next/static/ and public/. The .next/server/ folder (Node handlers that render HTML) stays on your server — that's the whole point. Your origin server keeps serving dynamic HTML; the CDN just handles the heavy static payload.
Yes. Set DASH4DEVS_BUILD_DIR=out in .env.local. Everything in out/ will be uploaded and served from the CDN.
Any file whose SHA-256 isn't already stored for your organization. This means branding assets, bundled code, or renamed chunks only upload once across all deploys.
Your first deploy uploads the whole bundle (typically 2-15 MB depending on dependencies). After that, only changed chunks are uploaded — usually 50-500 KB per code change.
No. Deploys require a secret sk_ key. The API rejects public keys for CDN endpoints.
The deployment stays in pending status and is not activated. Re-run dash4devs build — it will detect which files are still missing and only upload those. Nothing broken gets served.
Rollback by deploy ID is on the roadmap. For now, re-running dash4devs build against a previous commit of your codebase re-activates that version.