publish-artifacts
publish-artifacts
Turn a local folder of HTML artifacts into a live site at your domain, where the folder tree is the URL structure and each top-level folder is either public or locked to specific people by email one-time-PIN. Driven by one declarative manifest, safe to run from any machine.
Config — your specifics, in one place
Three values personalize this skill. They live in the manifest (the single source of truth). Nothing instance-specific is committed: the repo ships a generic worker/wrangler.toml.template, and init generates worker/wrangler.toml (gitignored) by substituting these values — wrangler can't read JSON, so this generation step is the bridge.
| Key | Example | Used for |
|---|---|---|
site |
ubuilt.dev |
the apex the Worker serves, and the host in every Access app domain |
bucket |
artifacts |
the R2 bucket that holds the objects |
worker |
ubuilt-artifacts |
the Worker name |
Throughout this doc ubuilt.dev, artifacts, and ubuilt-artifacts are concrete examples — read them as your Config values. To point the skill at a different domain: set these three in the manifest, then run setup (which regenerates worker/wrangler.toml from the template). The Worker code itself hardcodes nothing — it serves whatever the bound bucket holds.