Connect to GitMCloud¶
GitM depends on a companion service, GitMCloud, to authorize onboarding and to power the part-number registry and the browser BOM/assembly viewer. This page explains the client side of that connection; the GitMCloud app has its own section.
To set up or administer GitMCloud, see GitMCloud docs.
What GitM uses GitMCloud for¶
| Touchpoint | What happens | Hard dependency? |
|---|---|---|
| Onboarding access check | When you connect or create a repo, GitM calls a GitMCloud access endpoint to confirm your account is allowed. | Yes — fails closed. |
| Part-number registry | Numbers may be allocated by GitMCloud and stamped by GitM. | Only if you use part numbers. |
| BOM / assembly viewer | GitMCloud reads .gitm/ files to display BOMs and trees. |
Only for the browser viewer. |
The access check (important)¶
When you go through the wizard's connect or create flow, GitM contacts the GitMCloud access
endpoint at the configured base URL (https://gitmcloud.gojain.com in the current build) and
asks whether your GitHub account/owner is allowed.
- If allowed → onboarding continues.
- If denied → you see "GitMCloud: … Contact your administrator."
- If the endpoint is unreachable → onboarding is blocked (fail-closed). You see "Could not verify GitMCloud access."
There is no offline or bypass path. This is deliberate: access is gated centrally.
What you (the client) need¶
- Network access to the GitMCloud base URL from the workstation.
- Your GitHub account on the GitMCloud allowlist (an admin adds it on the GitMCloud side).
Steps if you're blocked¶
- Confirm the workstation can reach the GitMCloud URL (browser or
ping/curlthe host). - Ask whoever administers GitMCloud to confirm your account/owner is allowlisted.
- Retry the wizard.
Expected result¶
- The access check passes silently and the wizard proceeds to clone or create the repository.
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
| "Could not verify GitMCloud access: …" | Endpoint unreachable (network, DNS, firewall, service down). | Fix connectivity; confirm the service is up with your GitMCloud admin. |
| "GitMCloud: … Contact your administrator." | Account not on the allowlist. | Get added on the GitMCloud side. |
| Works for some users, not others | Allowlist is per-account/owner. | Add the missing accounts in GitMCloud. |
Known limitations¶
- Onboarding is fully dependent on GitMCloud. If GitMCloud is down, no one can connect or create a repository, even though the underlying storage is plain GitHub.
- The GitMCloud base URL is a build-time constant in the current release; changing it requires a new build. See Known limitations and discrepancies.