Setup
Three steps to get your first deploy ready.
Updated
On this page
1. Install the SDK
npm install dash4devs
This adds the dash4devs binary to ./node_modules/.bin. If you want it globally, install with -g or run it through npx.
Three steps to get your first deploy ready.
Updated
npm install dash4devs
This adds the dash4devs binary to ./node_modules/.bin. If you want it globally, install with -g or run it through npx.
Create .env.local in your project root (don't commit it):
DASH4DEVS_API_KEY=sk_live_your_secret_here
Optional overrides (all have sensible defaults):
DASH4DEVS_API_URL=https://api.dashfordevs.com
DASH4DEVS_BUILD_DIR=.next
DASH4DEVS_PUBLIC_DIR=public
/** @type {import('next').NextConfig} */
const nextConfig = {
assetPrefix: process.env.NEXT_PUBLIC_ASSET_PREFIX || undefined,
images: { unoptimized: true },
};
export default nextConfig;
That's the final piece. The CLI writes NEXT_PUBLIC_ASSET_PREFIX into .env.local after every successful deploy, so Next.js automatically picks up the CDN URL on the next build.
npx dash4devs status
If it prints "No active deployment for this organization yet", you're authenticated correctly and ready to run your first build.