CLI sites & buckets

Sites provide hosted identity and access. Buckets own files independently from the sites attached to them.

Sites

interfold sites list --status ACTIVE
interfold sites get <site-id>
interfold sites create --name "My Site" --access PRIVATE
interfold sites update <site-id> --access PUBLIC
interfold sites update <site-id> --reconcile

sites list accepts --account, --status, --limit, and --offset. sites create accepts --name, --access, --subdomain, --account, and --bucket.

List commands retain their resource name (sites or buckets) and include pagination. Use pagination.nextOffset for the next --offset; it is null on the final page.

Use sites get to read the actual subdomain before constructing a hosted URL. Do not guess it from the Site name.

--reconcile reseeds and retries durable per-path function and cron desired state. Ordinary executable file writes already reconcile immediately; --reconcile is the manual repair path for attachment, reactivation, or an exception that exhausted automatic retries. Inspect the returned status and deployment results before claiming the runtime is ready.

Buckets

interfold buckets list
interfold buckets create --name "My files"
interfold buckets get <bucket-id>
interfold buckets update <bucket-id> --name "Production files"

Attach an existing bucket during Site creation:

interfold sites create --name "My Site" --bucket <bucket-id>

Omitting --bucket creates storage automatically.

Access

A Site is PUBLIC or PRIVATE. Site access controls anonymous /web/ files; there are no per-file exposure overrides. Deployed /api/<name> runtimes are anonymously callable for either setting, so handlers must enforce their own authorization. Bucket and Files API access always requires account authentication.