Raypacks works without any config for most apps. When you need to override a default (a build entrypoint Raypacks can’t guess, for example), drop aDocumentation Index
Fetch the complete documentation index at: https://docs.withnubo.com/llms.txt
Use this file to discover all available pages before exploring further.
nubo.toml at the root of your repo.
Anatomy
nubo.toml
[build]
entrypoint
The path Raypacks builds from. Defaults to auto-detect.
- For Go: the directory containing your
main.go. Auto-detected from repo-rootmain.go, then the firstcmd/*/main.goalphabetically. - Other packs ignore this field today.
., ./path, or path/to/dir. Absolute paths and .. segments are rejected. The directory must contain a main.go.
nubo.toml
Precedence
Settings can come from three places. Higher beats lower:nubo.toml(committed to your repo)- Dashboard / API overrides (per-Frame, set in the UI or via
PATCH) - Raypacks auto-detection
nubo.toml checked into the repo is the source of truth. Dashboard tweaks fill in the gaps. Auto-detection is the fallback.
Validation
Raypacks rejects bad config at plan time, before the build runs. You’ll see a clear error in the build logs (“nubo.toml: build.entrypoint './cmd/missing' has no main.go”) rather than a confusing go build failure ten minutes later.
Inspecting the resolved plan
Every build prints a plan table that shows the final values and where each came from:decision line shows (auto) and you wanted something different, set the value in nubo.toml and redeploy.