# Vibehost Deploy > Deploy a static site or Next.js app to VibeHost and get a private shareable URL. Use when the user wants to ship, host, preview, or publish a built frontend or Next.js app. - Skill: `gntc-labs/vibehost-deploy` (Agent Skill) - Install (CLI): `npx skillmds@latest add gntc-labs/vibehost-deploy` - Raw SKILL.md: https://api.skillmd.com/api/skills/gntc-labs/vibehost-deploy/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: gntc-labs (https://skillmd.com/u/gntc-labs) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/gntc-labs/vibehost-deploy --- # Deploy to VibeHost Take a built static site or Next.js app and put it live on VibeHost at a private URL in seconds. ## When this skill applies The user says something like: - "ship this", "deploy this", "put this live", "host this", "publish this" - "get me a preview URL for this build" - "send this to staging / a demo link" Or you've just produced a static build output (`dist/`, `out/`, `build/`) or a Next.js build, and the natural next step is hosting it. If the user has no VibeHost account yet, point them at — deploying requires an authenticated session. ## Setup Install the CLI by downloading the installer, reviewing it, then running it — don't pipe it straight into a shell: ```bash # macOS / Linux; installs one static binary, user-level only (no sudo) curl -fsSL -o vibehost-install.sh https://vibehost.com/install.sh cat vibehost-install.sh # review it first: the script verifies the CLI binary's # SHA256 against the release manifest before installing sh vibehost-install.sh && rm vibehost-install.sh vibehost login # device-flow browser login; or VIBEHOST_TOKEN env var for headless/CI vibehost whoami # confirm session + which workspace is active ``` The installer writes only to `~/.vibehost/` and a bin shim in `~/.local/bin` — no shell-profile edits, no root. It sends an anonymous install beacon (platform, shell version, success/fail); opt out with `VIBEHOST_NO_TELEMETRY=1`. Auth can come from any of: a prior `vibehost login` (token in `~/.config/vibehost/config.json`), a `VIBEHOST_TOKEN` PAT in the environment (headless/CI), or an MCP OAuth session on `https://api.vibehost.com/mcp`. Most commands accept `--json` for scriptable output — prefer it when parsing. ## What VibeHost can host - **Static sites** (default runtime) — any directory with an `index.html` at its root (`dist/`, `out/`, `build/`, or plain HTML). - **Next.js apps (private beta)** — opt in with `--runtime nextjs`. App Router, SSR, ISR, server actions, and image optimisation are supported; prerender-only builds are auto-served via the static fast-path (no container). Apps that need a database can use the managed Postgres (`vibehost db`, Neon serverless) instead of an external DB. If `app create --runtime nextjs` returns `NEXTJS_RUNTIME_GATED`, the runtime is currently unavailable to this user/workspace (access can depend on platform, workspace, and user gates) — fall back to a static export (`output: 'export'` + deploy `./out`) or request access from the workspace owner. ## Recommended path: the CLI The `vibehost` CLI bundles app-creation, file hashing, blob upload, and the deploy into one command with progress output. Prefer it whenever you can run shell commands. ```bash vibehost app create my-app # once per app; name: lowercase, 2–40 chars, [a-z][a-z0-9-]* vibehost deploy ./dist --app my-app --json # every time # Next.js app instead of a static build (private beta — see above; server build by default): vibehost app create my-app --runtime nextjs --json vibehost deploy . --app my-app --json # sandboxed server build; no local next build required # Or explicitly build on the user's machine: vibehost deploy . --app my-app --build client --json ``` The `--json` output is `{ ok: true, data: { url, immutableUrl, ... } }`. The command exits 0 only after the deployment is healthy, so a successful exit means the URL is live. Tip: `vibehost link --app my-app` inside the project writes `.vibehost/project.json`, after which plain `vibehost deploy` works with no flags. ## Without a shell: the MCP server If you can't run a shell but have an MCP connection to `https://api.vibehost.com/mcp`, the deploy is a sequence of tool calls. **Read each tool's own `description` for the authoritative parameter schema** — the names and order are below, but don't hardcode argument shapes from this doc. 1. `list_apps` — find existing apps in the workspace. 2. `create_app` — only if the target doesn't exist (`{ name, workspaceId }`). 3. `check_blobs_missing` — pass the file SHA-256s; learn which the server still needs. 4. `request_upload` — mint pre-signed PUT URLs for the missing SHAs, then PUT the raw bytes to each (`Content-Type: application/octet-stream`) via plain HTTP. 5. `deploy` — `{ appId, channel?, manifest[] }`. Returns `{ deploymentId, status: "starting" }` **immediately** — the site is not live yet. 6. `get_deployment` — poll with `deploymentId` until `status` is `healthy` (live), `failed` (read the error), or `superseded`. ## What to give the user Always surface **both** URLs from the result: - **alias URL** (`url`) — tracks the latest deploy on this channel. Share this with people. - **immutable URL** (`immutableUrl`) — pinned to this exact build. Use for bug reports, review links, archived demos. ## Pitfalls - **No `index.html` at the root** — static deploys need one. For client-side-routed SPAs (React Router, Vue Router, Remix SPA mode), the edge has to serve `index.html` on path misses; see . Do **not** add a `_redirects` file — VibeHost doesn't parse it (that's a Netlify/Pages convention). - **Tarball rejected** — oversized or malformed builds raise `TARBALL_INVALID`; `error.details` says why. Trim large assets (videos, prod source maps, stray `node_modules`) or upgrade the plan. - **Wrong workspace** — a token scoped to workspace A deploying to an app in workspace B returns `TOKEN_WORKSPACE_MISMATCH`. Surface it; don't silently retry elsewhere. - **Discover ids, don't guess** — `appId` and `workspaceId` come from `list_apps` / `vibehost whoami` (or `list_workspaces`). Hardcoding a stale id fails; resolve it live each time. - **Read MCP tool schemas first** — when using the MCP path, the parameter shapes vary by tool and evolve over time. Read each tool's own `description` before calling it; don't assume argument shapes from this doc. - **Branch on `error.code`, not `error.message`** — codes are stable `SCREAMING_SNAKE_CASE`; messages can reword. - **Raw blob upload blocked by the edge WAF** — the CLI keeps `UPSTREAM_FAILED` but adds `details.kind = "blob_upload_blocked"`, the file path, and a `--no-chunked` hint. Retry with `vibehost deploy --no-chunked`; the gzip tarball path avoids content inspection of raw file bytes. ## Reference - Deploy guide: - CLI reference: - MCP server: - Error codes: