Deploying
Build & Start Commands
Override auto-detected build and start commands
Ink auto-detects build and start commands for most frameworks. You can override them when needed.
Auto-detection
For most projects, Ink reads your package.json, requirements.txt, go.mod, or equivalent to determine the right commands. For example:
- Node.js:
npm install && npm run build→npm start - Python/FastAPI:
pip install -r requirements.txt→uvicorn main:app - Go:
go build→./app
Custom commands
Your agent can specify custom commands when creating a service:
build_command— override the build step (e.g.,pnpm build)start_command— override the start step (e.g.,node server.js)
Publish directory
For single-page apps (React, Vue, etc.) that build to a static output:
Set publish_directory to the build output folder (e.g., dist, build, .next). Ink will build your app, then serve the output as static files.