Applying a Scaffold Config
Background
scaffold apply runs a declarative config file, so the whole setup can be reviewed, version-controlled, and reproduced by teammates with one command — this is the recommended way to scaffold an app and its services. The previous pages also show how to run the same steps as individual commands: scaffold app create, then scaffold service create per service. That's still fully supported and useful for one-off scaffolds or quick experiments, but typing out each command by hand doesn't leave you with anything to check into version control.
For the full command reference and config schema:
ApplySteps to Apply a Scaffold Config
Write .stoobly/scaffold.yml
Create a .stoobly/ directory in your app's root if it doesn't already exist, and write a config describing your app and its services:
# .stoobly/scaffold.yml
version: 1
commands:
- resource: app
action: create
options:
app_name: <APP-NAME>
# For E2E testing, add plugin: [playwright] or plugin: [cypress]
plugin: [playwright]
- resource: service
action: create
options:
service_name: <SERVICE-NAME>
hostname: <SERVICE-HOSTNAME>
scheme: <SERVICE-SCHEME>
port: <SERVICE-PORT>
# Add one service block per service. Repeat as needed.Validate with --dry-run
stoobly-agent scaffold apply .stoobly/scaffold.yml --dry-runThis checks the config's schema and each step's options without creating anything. Fix any reported errors before continuing.
A clean dry run means the config is well-formed — it doesn't guarantee the real apply will succeed, since some checks (like a required directory existing) only run when a command actually executes.
Next Steps
Now that your app and services are scaffolded, you can run workflows:
How to Run a WorkflowTo regenerate scaffold files after upgrading stoobly-agent, or to add more steps to your config later:
How to Update a ScaffoldLast updated