Skip to content
Browse documentation
reference

Configuration reference

Look up schema-1 project/workspace fields and the native tools or capability APIs that own other configuration.

Project manifest fields

smoothie.toml schema 1 describes project identity and local contracts, not runtime configuration. Each manifest declares exactly one of [project] or [workspace].

schemaRequired. Integer 1; other schema versions are rejected.
project.nameRequired project identity, unique within its workspace.
project.sdkSDK identifier. Use typescript for the current commercial selection.
contracts.imports[]Exact id (<namespace>:<name>) and positive major version.
contracts.exports[]id, major, format = json-schema, and a project-relative source path.

A project needs an SDK, a contract export, or both. The parser also recognizes python, go, rust, elixir and zig; recognition does not promise SDK support. A project may stand alone or be an explicit workspace member.

Workspace fields and validation

workspace.nameRequired workspace identity.
workspace.members[].pathExplicit relative project path; no globs. Must stay inside the workspace after symlink resolution.

Unknown schema-owned fields are rejected. Member paths and project names must be unique; contract sources stay inside their exporting project. Local imports must resolve to one compatible export. The manifest reader accepts at most 1 MiB of UTF-8 input.

For a minimal manifest and validation steps, use Configuration and environment. Project operations explains metadata inspection and native verification.

Configuration outside smoothie.toml

package.json / bun.lockDependency declarations, exact installed resolution and native scripts.
Native target filesBundler, router, HTTP host and deployment settings.
Capability constructionModel providers, credentials, queues, stores, policies and execution limits through the owning API.
vendor/smoothie recordsRetained release/package identity and Recipe adoption baseline; not another application configuration format.

There is no Framework-wide Config object or runtime-profile registry. Find capability options through the SDK package map; use native tool configuration for builds and dependencies.

Environment values and secrets

There is no global Framework environment-variable namespace or implicit dotenv loader. Each target or adapter documents the values it consumes. Browser build variables are public bytes; credentials belong in the server environment or native secret store. See Keep secrets server-only for the procedure.