Zero-config deployment for Bini.js projects - web, desktop, and mobile, all from one CLI.
bini-deploy scans your project, generates the right hosting configuration for your target platform, and pushes it straight to GitHub. No YAML spelunking, no platform-specific docs to read first.
Netlify, Vercel, Cloudflare Workers, Deno Deploy. Picks adapter, writes config, wires API routes.
Drop files in src/app/api/, bini-deploy scans and mounts each as route with dynamic segments.
API routes get permissive CORS headers out of the box on every non-Node adapter.
Windows, macOS, Linux, iOS, Android via Tauri with tailored next-step instructions.
Init repo if needed, sets up identity and auth if missing, commits and pushes.
Push failures diagnosed - bad credentials, repo not found, or diverged history with accurate recovery.
Run the CLI and answer the prompts:
It asks which platform you want to deploy to. Choose Web for any hosting provider:
If you picked Web, it then asks for the hosting provider:
Enter your repository URL (skipped when an origin remote already exists):
By default it pushes to the remote's default branch, falling back to main:
A confirmation prompt appears before generating files and pushing:
Finally, it asks for a commit message. Press Enter to use the default:
| Flag | Description |
|---|---|
| --platform <type> | web, windows, macos, ios, linux, android |
| --hosting <name> | node (default), netlify, vercel, cloudflare, deno (web only) |
| --repo <url> | GitHub repo URL, e.g. https://github.com/you/app |
| --generate-entry <host> | Generate production entry file only |
| --yes, -y | Skip prompts and use flags |
| --help, -h | Show usage information |
Examples:
| Provider | Runtime | Config Generated |
|---|---|---|
| Node.js (default) | Node (bini-server) | None - bini-server handles build/serve |
| Netlify | Edge Functions (Deno) | netlify.toml + netlify/edge-functions/api.ts |
| Vercel | Node.js Runtime | vercel.json + api/index.ts |
| Cloudflare Workers | Workers | wrangler.toml + worker.ts |
| Deno Deploy | Deno | server/index.ts |
Any file in src/app/api/ becomes an API route. Nested folders map to URL segments, bracket segments become dynamic params, and spread segments become wildcards:
If your route file imports from hono, bini-deploy detects it and mounts it as a full Hono app:
src/app/api/ directory for route filesuser.name/user.email once if not set, local only--allow-unrelated-histories -X oursZero-config deployment for Bini.js projects - web, desktop, and mobile, all from one CLI.
bini-deploy scans your project, generates the right hosting configuration for your target platform, and pushes it straight to GitHub. No YAML spelunking, no platform-specific docs to read first.
Netlify, Vercel, Cloudflare Workers, Deno Deploy. Picks adapter, writes config, wires API routes.
Drop files in src/app/api/, bini-deploy scans and mounts each as route with dynamic segments.
API routes get permissive CORS headers out of the box on every non-Node adapter.
Windows, macOS, Linux, iOS, Android via Tauri with tailored next-step instructions.
Init repo if needed, sets up identity and auth if missing, commits and pushes.
Push failures diagnosed - bad credentials, repo not found, or diverged history with accurate recovery.
Run the CLI and answer the prompts:
It asks which platform you want to deploy to. Choose Web for any hosting provider:
If you picked Web, it then asks for the hosting provider:
Enter your repository URL (skipped when an origin remote already exists):
By default it pushes to the remote's default branch, falling back to main:
A confirmation prompt appears before generating files and pushing:
Finally, it asks for a commit message. Press Enter to use the default:
| Flag | Description |
|---|---|
| --platform <type> | web, windows, macos, ios, linux, android |
| --hosting <name> | node (default), netlify, vercel, cloudflare, deno (web only) |
| --repo <url> | GitHub repo URL, e.g. https://github.com/you/app |
| --generate-entry <host> | Generate production entry file only |
| --yes, -y | Skip prompts and use flags |
| --help, -h | Show usage information |
Examples:
| Provider | Runtime | Config Generated |
|---|---|---|
| Node.js (default) | Node (bini-server) | None - bini-server handles build/serve |
| Netlify | Edge Functions (Deno) | netlify.toml + netlify/edge-functions/api.ts |
| Vercel | Node.js Runtime | vercel.json + api/index.ts |
| Cloudflare Workers | Workers | wrangler.toml + worker.ts |
| Deno Deploy | Deno | server/index.ts |
Any file in src/app/api/ becomes an API route. Nested folders map to URL segments, bracket segments become dynamic params, and spread segments become wildcards:
If your route file imports from hono, bini-deploy detects it and mounts it as a full Hono app:
src/app/api/ directory for route filesuser.name/user.email once if not set, local only--allow-unrelated-histories -X ours