Deployment Options

⚡One Command to Deploy Anywhere

bini-deploy makes deployment effortless. Simply run:

npm run deploy

When you run npm run deploy, bini-deploy will:

1. Prompt you to choose your target platform: Web, Windows, macOS, Linux, Android, or iOS
2. If you choose Web, it prompts for hosting provider: Node.js (default), Netlify, Vercel, Cloudflare, or Deno Deploy
3. Automatically generates the platform-specific configuration files and entry points
4. Commits and pushes everything to your GitHub repository

This single command works for all hosting platforms with zero configuration needed:

• Node.js — Builds and starts the server
• Netlify — Automatically generates netlify.toml and edge function entry
• Vercel — Automatically generates vercel.json and serverless function entry
• Cloudflare — Automatically generates wrangler.toml and worker entry
• Deno Deploy — Automatically generates server/index.ts entry

Node.js Server

The default deployment option. Bini.js uses bini-server — a zero-dependency production server.

npm run deploy

Your app will be served at the port specified by PORT (default: 3000).

Platforms

• Railway — Auto-detects Node.js, just connect your repo
• Render — Set build command to npm run deploy and start to npm start
• Fly.io — Use the Node.js builder
• VPS — Use pm2 to keep the server running

Netlify

Deploying to Netlify is completely automated with bini-deploy. No configuration needed.

npm run deploy

bini-deploy automatically generates:

• netlify.toml — Build and edge function configuration
• netlify/edge-functions/api.ts — API route handler for Edge Functions

Vercel

Deploying to Vercel is completely automated with bini-deploy. No configuration needed.

npm run deploy

bini-deploy automatically generates:

• vercel.json — Routing and build configuration
• api/index.ts — Serverless function entry point

Cloudflare Workers

Deploying to Cloudflare Workers is completely automated with bini-deploy. No configuration needed.

npm run deploy

bini-deploy automatically generates:

• wrangler.toml — Worker configuration
• worker.ts — Worker entry point with API routes

Or deploy manually with Wrangler:

npx wrangler deploy

Deno Deploy

Deploying to Deno Deploy is completely automated with bini-deploy. No configuration needed.

npm run deploy

bini-deploy automatically generates:

• server/index.ts — Deno Deploy entry point

In the Deno Deploy dashboard, set:

• Entrypoint: server/index.ts
• Build Command: npm run deploy
• Runtime: Dynamic App

Static Export

For static hosting, export your app as HTML files (this is the only deployment method that doesn't use npm run deploy):

npm run export

The exported files will be in the dist/ folder. Suitable for:

• GitHub Pages
• Amazon S3
• Firebase Hosting
• Cloudflare Pages (static mode)
• Netlify (static mode)
• Vercel (static mode)

GitHub Pages

Set the base option in vite.config.ts if deploying to a subpath:

// vite.config.ts
export default defineConfig({
  base: '/your-repo-name/',
  plugins: [react(), biniExport()],
})

Platform Comparison

Environment Variables in Production

Set environment variables through your hosting platform's dashboard:

Best Practices

• Test builds locally — Run npm run build and npm run preview before deploying.
• Use environment variables — Keep configuration separate from code.
• Set up CI/CD — Automate deployments with GitHub Actions or similar.
• Monitor your app — Use platform analytics to track performance.
• Use a custom domain — Configure SSL for secure connections.