Config File Spec

floo uses two config files: floo.service.toml for single-service apps and floo.app.toml for multi-service apps or apps with managed services. floo init creates these files. This page is the full reference.

Config shapes

Shape	Files	When to use
Single service	`floo.service.toml`	One service, no managed services
Single service + managed	`floo.app.toml`	One service with Postgres, Redis, or Storage
Inline multi-service	`floo.app.toml`	All services defined in one file
Delegated multi-service	`floo.app.toml` + per-service `floo.service.toml`	Service config lives alongside service code

Single service

[app]
name = "my-app"
access_mode = "public"

[service]
name = "web"
type = "web"
port = 3000
ingress = "public"
env_file = ".env"

[resources]
cpu = "1"
memory = "512Mi"
max_instances = 10

Single service with managed services

[app]
name = "crm"

[postgres]
tier = "basic"

[redis]

[storage]

[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"

Inline multi-service

[app]
name = "full-stack"
access_mode = "password"

[postgres]
tier = "basic"

[redis]

[resources]
cpu = "1"
memory = "512Mi"
max_instances = 10

[services.web]
type = "web"
path = "./web"
port = 3000
ingress = "public"

[services.api]
type = "api"
path = "./api"
port = 8080
env_file = "./api/.env"

[services.worker]
type = "worker"
path = "./worker"
port = 8081
ingress = "internal"
cpu = "2"
memory = "2Gi"

Inline and delegated are mutually exclusive per service. If a service has type and port in floo.app.toml, do not also place a floo.service.toml in that service’s directory. The CLI rejects this during preflight.

Delegated multi-service

Root floo.app.toml:

[app]
name = "full-stack"

[postgres]

[services.web]
path = "./web"

[services.api]
path = "./api"

web/floo.service.toml:

[app]
name = "full-stack"

[service]
name = "web"
type = "web"
port = 3000
ingress = "public"

api/floo.service.toml:

[app]
name = "full-stack"

[service]
name = "api"
type = "api"
port = 8080
ingress = "public"
env_file = ".env"

Field reference

`[app]`

Field	Type	Default	Description
`name`	string	required	App name (DNS-safe)
`access_mode`	string	`"public"`	`public`, `password`, `accounts`, `sso`

`[service]` (floo.service.toml only)

Field	Type	Default	Description
`name`	string	required	Service name (DNS-safe, 2-21 chars)
`type`	string	required	`web`, `api`, `worker`
`port`	integer	required	Port the service listens on
`ingress`	string	`"public"`	`public` or `internal`
`env_file`	string	none	Relative path to env file synced on deploy

`[services.<name>]` (floo.app.toml)

Same fields as [service] above, plus:

Field	Type	Default	Description
`path`	string	required	Relative path to service directory
`dev_command`	string	none	Shell command run by `floo dev` to start the service locally. Example: `"npm run dev"`
`migrate_command`	string	none	Shell command run before `floo dev` starts the service (and after each deploy). Example: `"alembic upgrade head"`
`domain`	string	none	Custom domain for this service. Example: `"api.example.com"`

`[resources]`

Field	Type	Default	Description
`cpu`	string	`"1"`	vCPU allocation
`memory`	string	`"512Mi"`	Memory allocation
`max_instances`	integer	`10`	Max instance count

Per-service resource fields override the global [resources] section.

`[postgres]`, `[redis]`, `[storage]`

Field	Type	Default	Description
`tier`	string	`"basic"`	`basic`, `standard`, `performance`

Managed services are top-level sections in floo.app.toml. They are not placed under [services.*].

`[auth]`

Field	Type	Default	Description
`redirect_uris`	array	none	OAuth callback URLs for `accounts` mode

`[environments.<name>]`

Field	Type	Default	Description
`access_mode`	string	none	Override access mode per environment

Precedence

When you run a command without --app, the CLI resolves the app in this order:

--app <name> flag
Nearest floo.service.toml
Nearest floo.app.toml

Access mode resolution:

[environments.dev].access_mode
[app].access_mode in floo.app.toml
[app].access_mode in floo.service.toml

Resource precedence: per-service values override global [resources].

Validation

floo deploy --dry-run --json

The CLI fails preflight if:

service names are duplicated
a service port is invalid
an inline service also has a floo.service.toml in its directory
a multi-service app has no public service
managed service sections are placed in floo.service.toml instead of floo.app.toml

CLI

Config

​Config shapes

​Single service

​Single service with managed services

​Inline multi-service

​Delegated multi-service

​Field reference

​[app]

​[service] (floo.service.toml only)

​[services.<name>] (floo.app.toml)

​[resources]

​[postgres], [redis], [storage]

​[auth]

​[environments.<name>]

​Precedence

​Validation