Skip to main content
This page lists every field brimble.toml accepts. For how the file is applied on push, approvals, environments, and previews, see Configure projects with brimble.toml.

Value formats

Sizes and durations must include a unit. memory = 1 and for = 300 are invalid; write memory = "1gb" and for = "5m". Unknown fields are rejected, so a typo fails the deploy with the line number instead of being ignored.

File layout

Services

[services.<name>]

Build

[services.<name>.build] All build fields apply automatically. See Builds.

Deploy

[services.<name>.deploy] All deploy fields apply automatically.

Resources

[services.<name>.resources] CPU and memory are metered.

Scale

[services.<name>.scale] Use either a fixed replica count or autoscaling, not both. Applies automatically. Requires a plan with autoscaling. See Scaling.

Cron

[services.<name>.cron], web services only.

Volume

[services.<name>.volume] Requires a plan with volumes. See Persistent disk.

Environment variables

[services.<name>.env]
Names must start with a letter or underscore and contain only letters, numbers, and underscores. Values are strings and support references. Referencing a database or bucket defined in the file links it to the service. Variables set only in the dashboard are left alone. Never put secret values here.

Secrets

[services.<name>.secrets]

Files

[[services.<name>.files]], repeat for each file. The file is read from the pushed commit on each deploy. See Files.

Network

[services.<name>.network] Domains are only added, never detached, when you remove them from the file. Custom domains, wildcard domains, and previews each need a plan that includes them. Redirects
status is one of 301, 302, 307, or 308. See Redirect a domain. Cache, headers, and firewall
See Networking. Rate limits [[services.<name>.network.rate_limits]], repeat for each rule. Requires a plan with rate limiting. See Rate limits.

Alerts

[[services.<name>.alerts]], repeat for each alert. Requires a plan with alerting. See Notifications.

Log drains

[services.<name>.drains] Requires a plan with log drains. See Log drains.

Databases

[databases.<name>] engine and version are required to create a database. Backups
Connection pool [databases.<name>.pool], requires pgbouncer = true. Pool settings apply automatically. High availability
regions lists at least two regions. High availability is set when the database is created and requires a plan that includes it. See Deploy a database.

Buckets

[buckets.<name>]
See Object storage.

Environments

[environments.<name>], where <name> is the workspace environment’s slug. Lists replace the inherited list rather than merging with it.

Pull request previews

[environments.preview.services.<name>] accepts only these tables:

Full example

Last modified on September 30, 2026