Deployables
A Deployable is one app: one entry document in one branch of one repository, served at one URL, with one set of access rules.
What it holds
Section titled “What it holds”| Part | Notes |
|---|---|
| Source | A repository and branch. Your git provider stays the source of truth. |
| Entry path | The index.html to serve. Its folder becomes the site root. |
| Version | The commit served, pinned to a branch, a release, or a commit id. |
| URL | Stable for the life of the Deployable. |
| Owner | The person or group that manages it. |
| Sharing scope | Who can open it, from just you to anyone with the link. |
| Secrets and API targets | Credentials, and the origins they may be sent to. |
| Catalog metadata | Name, description, and tags used for discovery. |
What it runs
Section titled “What it runs”Static files, read from your repository. Stackboard runs no build and no server code; your code runs in the visitor’s browser, sandboxed, with network access limited to the APIs you configure. Data ships with the repository or comes from those APIs. See Limitations.
Versions
Section titled “Versions”A Deployable serves a commit. Follow a branch and each push is picked up, or pin to a release or a commit id so it changes only when you say so. Pinning to a release records the commit that release pointed at, since a tag can be moved later and a commit id can’t.
One or several
Section titled “One or several”One Deployable per tool. Sharing is set per Deployable, so bundling unrelated
tools over-grants access to at least one of them. Several Deployables can point
at the same repository with different entry paths, and a second one on a
staging branch gives you somewhere to test.