Apps
An app is one site, served from one branch of one repository at a URL of its own, with its own rules about who can open it. For example, a dashboard, a decision tool, or anything that calls an API.
What it holds
Section titled “What it holds”| Part | Notes |
|---|---|
| Source | A repository and branch, and the git account that reads them. 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 app. |
| Owner | The person or group that manages it. |
| Who can open it | Specific users, Internal, or External. |
| Secrets and API targets | Credentials, and the origins they may be sent to. |
| Catalog listing | Whether it is published, and the 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.
The git account
Section titled “The git account”An app reads its repository through one git account, chosen under Source. An app added by URL uses an access token pasted for it instead, or nothing at all for a public repository. That token belongs to the app, so any of its owners can keep it.
Transferring the app clears its account or token, and the new owner chooses their own. Disconnecting an account in Settings → Integrations removes it from every app that used it. Until one is chosen, an app on a private repository stops working.
To change the source, you need an account of your own that can read the repository. Until you choose one, the repository, branch, and entry file are read-only, which stops anyone from pointing another user’s account at a repository of their choosing.
Versions
Section titled “Versions”An app 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 app per tool. Sharing is set per app, so bundling unrelated
tools over-grants access to at least one of them. Several apps can point
at the same repository with different entry paths, and a second one on a
staging branch gives you somewhere to test.