Build from a clean tree
The build command should work without editor state, local caches, or undeclared tools.
Guidesadios.yaml
Manifest guide
One manifest from AI-assisted source to live app.
`adios.yaml` keeps the deploy contract beside the code: build, start, port, health, secrets, resources, replicas, and routes. That makes generated changes easier to review before they reach production.
adios.yaml
name: billing-api
region: de
replicas: 2
build_cmd: pnpm install && pnpm build
start_cmd: pnpm start
runtime:
name: node@24
port: 3000
health_path: /api/health
requires:
- db
secrets:
DATABASE_URL: secret://DATABASE_URL
API_SIGNING_KEY: secret://API_SIGNING_KEYDeploy contract
Review the manifest like production code.
Application code and deploy configuration change together. A small manifest keeps the operational parts visible in source review instead of scattering them across a chat transcript, dashboard, and shell history.
| Field | What to check |
|---|---|
| name | Stable app name used by Adios for the workload. |
| build_cmd | Command that prepares production assets from a clean checkout. |
| start_cmd | Command that starts the production process. |
| runtime.port | Port the app listens on inside the runtime. |
| runtime.health_path | HTTP path Adios can use to test readiness. |
| secrets | Secret references such as secret://DATABASE_URL. |
| requires | Managed services the app depends on, such as db or cache. |
Workflow
Use the manifest to keep AI output deployable.
When an AI agent adds an API route, background worker, database call, or external provider, ask it to update the manifest only when the runtime contract changes. Then verify the command and config instead of trusting the generated file blindly.
Start the production server
The start command should run the server process that will receive real traffic.
Probe readiness
The health path should fail when required request-path dependencies are unavailable.