For publishers¶
The Publisher is whoever builds and ships GitM and GitMCloud. Today that is the project owner — not a customer. This section is the operational guide for everything the Publisher owns end to end: compiling the add-in, producing the installer, deploying the web app, registering the GitHub apps, and migrating the whole setup to a new account.
Publisher vs Customer — keep these straight. The rest of this documentation (Designers, CAD admins, IT admins, Installation, GitMCloud usage) is written for customers — the teams who use GitM. This section is for the one party who produces and operates it. If you are installing GitM to use it, you are in the wrong section — see Installation instead.
Who does what¶
| Publisher (you) | Customer (an Owner + their team) | |
|---|---|---|
| GitM add-in | Builds the DLLs and the installer .exe |
Installs the .exe on workstations |
| GitMCloud | Deploys it (Vercel, Firebase, domain) | Connects to it in a browser |
| GitHub OAuth App | Registers it once | — (just signs in) |
| Supplier Exchange GitHub App | Registers it once | Installs it once per Owner |
| Access allowlist | Sets ALLOWED_OWNERS |
— (must be on the list to connect) |
| Accounts | One publisher GitHub account (owns the apps + code) | One customer GitHub Owner per company |
The tenant boundary is the Owner — one customer = one GitHub Owner (user or org), owning many repos. The Publisher serves many customers from a single GitMCloud deployment and a single distributed installer.
What the Publisher owns¶
- The code repositories —
GitM(add-in) andGitMCloud(web app). - A Vercel project building and hosting GitMCloud at
gitmcloud.gojain.com. - A Firebase project (Firestore + Realtime Database) backing Supplier Exchange and live icon refresh.
- A GitHub OAuth App (the "Sign in with GitHub" button).
- A GitHub App for Supplier Exchange — planned; see Register the GitHub apps.
- The
ALLOWED_OWNERSallowlist that gates who can onboard. - The
gojain.comcustom domain and its DNS.
Publisher tasks¶
| Task | Page |
|---|---|
| Build the add-in DLLs | Build the GitM add-in |
Produce the installer .exe |
Create the installer exe |
| Deploy / operate the web app | Deploy GitMCloud |
| Register the OAuth + Exchange apps | Register the GitHub apps |
| Move everything to a new account | Migrate the publisher account |
For code-level detail (project layout, runtime constraints, data contracts), see
DEVELOPER.mdin each repository. This section is operational — how to ship and run, not how to modify the code.