Configuration

A repository tells Trevize how to set itself up, run, and preview through a single file: .trevize/settings.json. It lives in your repo, is versioned alongside your code, and controls what happens inside every sandbox Trevize creates for a session or automation.

• Overview & schema — the shape of settings.json and what each top-level key does.
• Hooks — commands that run at sandbox lifecycle points such as SandboxReady (install dependencies, select a runtime, run setup).
• Preview targets & processes — declare the processes that serve your app so reviewers get a live preview (command, port, env, defaultProcess).
• Resources — attach managed resources such as a Neon database and map their connection details into environment variables.
• Annotated example — a complete settings.json walked through section by section.

For the exhaustive field list, see the settings.json reference.