Publish site
deployDestructive
Publish a static site. New: every file, or template. Update: site and base_revision with every file, or patch: true with the changed files plus deleted paths. With site and upload: true: a link where the user uploads photos instead.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site | No | Site name, e.g. brave-otter-4821 | |
| files | No | ||
| patch | No | true: files are only the changed ones | |
| folder | No | With upload: target folder (default images) | |
| upload | No | With site: a 1-hour upload link for the user instead of deploying; get_site lists the files after | |
| deleted | No | patch only: paths to remove | |
| template | No | Template name, e.g. "brasa": its files become the site (files given replace those paths); then patch-deploy edits | |
| workspace | No | New sites: create it in this workspace (id or name from get_account) | |
| site_token | No | site_token from the first deploy (anonymous sites only) | |
| base_revision | No | ||
| idempotency_key | No | New sites: a fresh random value (e.g. a UUID); a retry with the same key and files replays the first result |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | On failure (isError): {code, message} | |
| agent_message | No | ||
| confirm_token | No |