Prepare GitMCloud before installing GitM¶
Before installing GitM on your team's machines, your team needs GitMCloud configured. GitM's first-run wizard calls a GitMCloud access endpoint when a user connects or creates a repository, and it fails closed — if GitMCloud is unreachable or the user isn't allowlisted, onboarding is blocked. Installing GitM on a hundred machines does no good if no one can get past the wizard.
GitMCloud is a separate app. Setting it up, hosting it, and managing its allowlist are covered in its own section: GitMCloud docs — in particular Deploy GitMCloud and Manage the access allowlist.
What GitM expects from GitMCloud¶
- A reachable GitMCloud deployment at the base URL the GitM build is configured for. In the
current build that is
https://gitmcloud.gojain.com, and the wizard calls its access-check endpoint. - An allowlist that includes the GitHub accounts (or repository owners) of everyone who will onboard.
Your checklist before rolling out GitM¶
- Confirm GitMCloud is deployed and reachable from inside your network, at the base URL the GitM build targets.
- Allowlist your users on the GitMCloud side (their GitHub accounts / owners).
- Confirm network/firewall allows the workstations to reach the GitMCloud host over HTTPS.
- Only then deploy GitM.
Why this matters¶
The access check has no offline path and no bypass. This is intentional — access is gated centrally through GitMCloud. The practical consequence for IT: GitMCloud readiness is a blocking prerequisite for a GitM rollout, on the same level as having Git installed.
Expected result¶
- A test user on a test machine can complete the GitM wizard's connect flow without a GitMCloud access error.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| Every user blocked with "Could not verify GitMCloud access" | GitMCloud unreachable from the network. | Fix connectivity/DNS/firewall to the GitMCloud host; confirm the service is up. |
| Some users blocked with "GitMCloud: … Contact your administrator." | Those accounts aren't allowlisted. | Add them on the GitMCloud side. |
| Works on your machine, not on a locked-down workstation | Egress firewall blocks the GitMCloud host. | Allow HTTPS to the GitMCloud base URL. |
Known limitations¶
- GitMCloud is a hard dependency for onboarding. There is no way to let a user connect a repository while GitMCloud is down.
- The GitMCloud base URL is compiled into the GitM build (a deployment constant). Pointing GitM at a different GitMCloud requires a new build. See Known limitations and discrepancies.