Skip to main content

Props

A Prop is a connected Git repository. Fibe clones it for builds, mounts it for dev, triggers Tricks on push.

Without a Prop, a Template can still be a static image: recipe. With one, the Template gets dynamic — branches, commits, hot-reloaded source, push-triggered jobs.

What a Prop gives you​

CapabilityDetail
Branch discoveryEvery branch listed for launchers to pick.
Source for buildsTemplates that say fibe.gg/repo_url: <this prop> clone at launch.
Live source mountDev services mount the working tree. Edits show up live.
Compose detectionOn connect, Fibe notices fibe.yml, fibe.yaml, docker-compose.yml, or docker-compose.yaml at the repo root and .env.example. Candidates for new Templates.
Push notificationsRefresh branch list, fire source-linked Templates that track changed files, trigger listening Tricks.
In-browser gitStage, commit, push from the Playground terminal.
Per-commit historyWhat landed and when.

Supported providers​

Two providers, each with its own auth path:

ProviderURL shapeAuth
Built-in GiteaURL inside Fibe's Gitea hostAuto-provisioned per Player — one built-in Git connection per account. No setup.
GitHubhttps://github.com/owner/repo or ssh://…GitHub App installation, or per-Prop Personal Access Token.

Other providers (GitLab, Bitbucket, self-hosted) aren't supported today. The repo-URL validator only accepts the two above. To use code from another host, push a mirror into the built-in Gitea.

Connect a GitHub repository​

Three ways, in order of preference:

Best when you have multiple private repos in the same org and want webhooks + CI to work without per-Prop token management.

  1. Go to Profile → Advanced Settings → GitHub Apps, click Install on GitHub.
  2. GitHub asks which org/account and which repos to grant.
  3. Pick repos. Return to Fibe; the installation is registered.
  4. Create a Prop from any granted repo — no token needed. Fibe mints short-lived installation tokens at clone time.

Multiple installations per account are supported (one per org or repo set). Detail: Advanced → GitHub Apps.

2. Sign in with GitHub​

Best when you mostly use your own (personal) repos and want a single OAuth click.

  1. Click Connect GitHub from the profile. GitHub OAuth flow runs.
  2. Your GitHub user is linked. Public repos clone without further setup; private ones still need an App installation or a PAT.

3. Paste a Personal Access Token (per-Prop)​

Best for one-off integrations or when you can't install the App (no admin rights on the org).

When creating a Prop from the GitHub Repository tab:

  • Repo URL — https://github.com/owner/repo (an ssh://… URL also works).
  • Default branch — defaults to the repo default.
  • Credentials (Personal Access Token) — paste a PAT.
    • Classic PAT with the repo scope, or a fine-grained PAT scoped to the specific repo with the relevant permissions (contents read/write, metadata read).
    • Format ghp_… (classic) or github_pat_… (fine-grained).
    • Stored encrypted on the Prop. Used at clone time and for the API calls the Prop needs (read/write contents, metadata).

PATs are per-Prop and don't share across Props. Rotate from the Prop's settings page when the token expires.

When both an App installation and a PAT are available, the PAT wins. The Prop uses what's set on its credentials field; if blank, it falls back to the App installation token.

Connect a built-in Gitea repository​

Fibe runs an internal Gitea instance and provisions an account for every Player automatically.

Auto-provisioning​

The moment your Player is created, a background job runs:

  1. Creates a Gitea user matching your Fibe username.
  2. Generates a random password and saves it to your profile's Gitea account card.
  3. Mints a Gitea access token with repository read/write plus user access scopes.

You don't take any action. When the job finishes you'll see a toast: "Your Gitea account has been provisioned. Check your profile for credentials."

Where the Gitea credentials live​

Profile page shows a Gitea account card:

  • Username — same as your Fibe username.
  • Password — the random one generated at provisioning. Copy it from the card. Hidden by default; click to reveal.
  • Profile — link to your Gitea profile page.
  • Sign in — link to the Gitea sign-in page. Gitea uses a separate session from Fibe.

Use these to log into Gitea directly (push from the command line, browse the web UI, etc.).

Reset credentials​

If you lose the password or want to rotate:

  1. Profile → Reset credentials on the Gitea card.
  2. 2FA confirmation required.
  3. Fibe generates a new password and a new access token for your Gitea account; reset tokens carry write:repository, read:repository, write:user, and read:user access. The new password appears on the card, and all your Gitea Props pick up the new token automatically. (A token you pasted into a specific Prop's Credentials field is not touched.)

Creating a Gitea repo​

From New Prop → New Repository tab:

  • Repo name — letters, digits, dashes, underscores, or dots; must be unique in your Gitea account (e.g. my-new-app).
  • Private — toggle.
  • Click Create Repository. Fibe creates the repo in Gitea and saves the Prop.

The repo is owned by your Gitea user. You can push to it via HTTPS using your Gitea credentials or access token. The built-in Gitea does not offer SSH access.

Provisioning failures​

Provisioning retries automatically (polynomial backoff, up to 10 attempts for connection issues), and Fibe also keeps retrying in the background every few minutes. While provisioning is pending, the profile shows a Gitea badge with a spinner — click it to trigger a retry immediately.

What's auto-set up on connect​

Whatever the provider and auth path, on creation Fibe:

  1. Resolves the repo URL. Validates the format.
  2. Discovers branches.
  3. Notes useful files (fibe.yml, fibe.yaml, docker-compose.yml, docker-compose.yaml, and .env.example) as candidates for new Templates.
  4. Wires up push notifications where possible — automatic when Fibe creates the repository for you (built-in Gitea). For GitHub, push events are delivered through the Fibe GitHub App — install the App on the repo to get branch refresh and push-triggered Tricks. A Prop connected with only a Personal Access Token does not receive push events.

Pushes​

On commit, Fibe:

  1. Refreshes the branch list.
  2. Auto-publishes new Template versions for any source-linked Template tracking a changed file.
  3. Fires Tricks configured for that push or PR.
  4. Posts a commit notification to your inbox — gated by the Prop's Notifications toggle, on by default. See Inbox Notifications.

Push delivery is managed automatically — through the built-in Gitea's webhook or the Fibe GitHub App.

Branch deletions are mirrored too. Delete a branch upstream and Fibe drops it from the Prop's branch list automatically — re-push the branch to bring it back.

Editing source from a Playground​

Playground terminal has full git tooling. The UI exposes a diff view, commit message field, push button.

Commits go back to the Prop. The push notification fires. Source-linked Templates and Tricks react.

Props are personal​

Each Player owns their Props. Two people can connect the same upstream repository independently, with separate credentials, branches, and Trick configurations.

If you fork a Template that points at someone else's Prop, your fork doesn't get access to their repository. Connect your own Prop (or a fork of theirs).

Source-linked Templates​

A Template can point at a file in a Prop — typically the Compose file at the repo root. Two effects:

  1. Auto-publish on file change. New commits touching the file → new Template version. Body is the file at that commit.
  2. CI Trick. Enable CI on the Template and Fibe creates a Trick that runs against the latest version on push or PR.

See Playspecs → Source-linked Templates for full detail.

FAQ​

Which is better — GitHub App or PAT?

App, when you can install it: installation tokens are short-lived, scoped per-installation, and webhook delivery is managed centrally. PATs are convenient when you can't install the App (no org admin rights) or for one-off Props.

Can I use a PAT for an arbitrary git host (GitLab, Bitbucket, self-hosted)?

No. The credentials field works only for GitHub URLs. The URL validator rejects other hosts. To bring code in from elsewhere, push a mirror to the built-in Gitea.

Fine-grained vs classic PAT?

Both work. Fine-grained is preferred — you can scope it to one repo and one set of permissions. Classic PATs grant repo scope, which covers all of your repos at once.

What happens when a PAT expires?

Clones and the Prop's API calls fail. The Prop surfaces an authentication error on the next sync. Paste a fresh PAT into the Prop's Credentials field to fix.

Rotate credentials on a Prop?

Yes. Re-authenticate (or paste a new PAT) from the Prop settings. Fibe stops using the old token immediately — revoke it on GitHub if you want it dead.

Where's my Gitea password if I never saved it?

Profile → Gitea account → reveal Password. If the password isn't visible ("Password is not saved for this account"), click Reset credentials to mint a new one.

Can I SSH into Gitea?

No. The built-in Gitea is HTTPS-only — SSH is disabled. Clone and push over HTTPS using your Gitea username and password (or access token) from the profile card.

Are repos created through Fibe public or private?

In the New Repository tab you choose with the Private toggle. When automation creates the repo and you don't specify — e.g. the SDK's greenfield flow — built-in Gitea repos default to private and GitHub repos default to public. Pass the privacy flag explicitly to override either default.

Deleted Prop?

You can't delete a Prop while any of your Playspecs reference it — the delete is refused and the message names the Playspecs. Remove or repoint those Playspecs first, then delete the Prop.

Last updated on