PlaidCloud Git Connection

A PlaidCloud Git connection points a workflow — or a Server Panel app’s build — at a repository on your workspace’s own managed Git server. Because that Git server is hosted for you at git.<your-workspace>.plaid.cloud and you’re already signed in through your normal PlaidCloud login, the connection form is far simpler than an external Git provider’s: there’s no server URL to enter and no username, token, or SSH key to manage.

Note

You never enter a server URL or credentials for a PlaidCloud Git connection. Your workspace’s Git server and your access to it are handled automatically from your PlaidCloud sign-in (including SSO) — so there are no tokens to mint, store, or rotate.

When to Use It

Reach for a PlaidCloud Git connection whenever the repository you want to read from lives in PlaidCloud Git — your workspace’s built-in Git service — rather than on an outside host. The most common use is to automate server Panel app or Dash app builds from a managed repository, so a push to a branch rebuilds and redeploys the app without an external GitHub account or personal access token in the loop.

For a repository hosted on an outside service — GitHub, GitLab, Bitbucket, Forgejo, or Gitea — use an external Git connection instead. Those keep the full form with a Server URL, user/token or SSO authentication, and SSL and SSH tabs.

Create a PlaidCloud Git Connection

1. Open Tools > Connections
2. Click New Connection and choose PlaidCloud Git from the menu
3. Fill in the simplified form:
   • Account Name — a display name for the connection
   • Memo — an optional note about what the connection is for
   • Repository — click Refresh to list the repositories your workspace can reach, then choose one (for example your udfs or apps repository). You pick from the list rather than typing the path.
   • Default Branch — choose the branch to read from by default from the list of branches in the repository you selected
   • Start Path — optionally browse the repository and choose a folder to scope every file lookup to a subfolder; leave it unset to use the whole repository
4. Set Usage — Active to enable the connection, and Read Only if the connection should never write
5. Set the Security Model — who in the workspace may use the connection
6. Click Create to save

That’s the whole form. Unlike an external Git provider, there is no Server URL, no authentication tab, and no SSL or SSH configuration — those are all handled for you.

Note

The Repository, Default Branch, and Start Path are chosen from live lists — pick a repository first, then its branch, then browse to a folder — so there’s nothing to mistype. Each list is read using the connection’s own access, so for a PlaidCloud Git connection they populate straight away with no credentials to enter.

Security Model

The Security Model controls who in the workspace can use the connection:

Option	Who can use the connection
Private (Only Owners)	Just the owners.
Specific Members Only	Owners plus an explicit list of members.
Specific Security Groups Only	Owners plus members of named security groups.
All Workspace Members	Everyone in the workspace.

For Specific Members Only or Specific Security Groups Only, grant the access from the list’s Actions menu after saving. See Create and Manage a Connection for the shared connection mechanics.

Automate Panel App and Dash App Builds From Managed Git

A server Panel app or a Dash app builds from a Git branch and rebuilds automatically on every push to that branch. Pointing it at a PlaidCloud Git connection keeps the whole loop inside your workspace — no external host and no personal access token to keep alive.

1. Push your app to a repository on your workspace’s PlaidCloud Git server — an entry-point .py file (Panel’s calls .servable(); Dash’s exposes server = app.server), and an optional requirements.txt at the repository root or next to your entry point. See Creating a Panel App or Deploy a Dash App From PlaidCloud Git for the repository layout.
2. Create a PlaidCloud Git connection whose Repository is that repository, following the steps above.
3. In My Panel Apps, click New Server App or New Dash App and, under Git Connection and Publish Watcher:
   • Git Connection — choose the PlaidCloud Git connection you just created
   • Branch — the branch to build from; pushes to it rebuild and redeploy the app
   • Entry Point — the .py file the app should serve
4. Finish the publish dialog and click Publish.

From then on, every push to that branch on your managed Git server rebuilds the app — an end-to-end automated build that never leaves PlaidCloud.

Related

• Deploy a Panel App From PlaidCloud Git — the end-to-end path from repository to a served app.
• Deploy a Dash App From PlaidCloud Git — the same path for a Plotly Dash app.
• Create and Manage a Connection — the shared form, environments, testing, and access controls.
• Creating a Panel App — publish and rebuild a Server Panel app from a Git branch.
• PlaidCloud Git — your workspace’s built-in Git service.
• Git Repository Connections — external Git providers and their full connection forms.