sync: auto-sync from ACG-TECH03L at 2026-04-19 12:50:13

Author: Howard Enos
Machine: ACG-TECH03L
Timestamp: 2026-04-19 12:50:13
This commit is contained in:
2026-04-19 12:50:15 -07:00
parent c44a01f5dd
commit c4fdb5a233
13 changed files with 2238 additions and 47 deletions

View File

@@ -4,50 +4,4 @@ Check this file at sync. Delete items after you've addressed them.
---
## 2026-04-18 — GuruRMM is now a git submodule
The `projects/msp-tools/guru-rmm/` folder is no longer tracked as regular
files in claudetools. It is now a git submodule pointing to the live gururmm
Gitea repo. You need to initialize it on ACG-TECH03L.
**Run this once after pulling:**
```bash
cd D:/claudetools # or wherever your claudetools checkout is
git submodule update --init projects/msp-tools/guru-rmm
```
This clones the full gururmm repo into that folder. After that, pulling
claudetools will NOT automatically update the submodule — you need to
run this to get the latest gururmm code:
```bash
git submodule update --remote projects/msp-tools/guru-rmm
```
**Working on gururmm code going forward:**
```bash
cd projects/msp-tools/guru-rmm # this is now its own repo
git pull # get latest
# make changes, commit, push as normal
cd ../../../ # back to claudetools root
git add projects/msp-tools/guru-rmm
git commit -m "chore: update gururmm submodule pointer"
```
**Why this changed:**
The old copy in claudetools was drifting behind the live repo on the server.
Features were being built in the gururmm repo that session logs in claudetools
marked as "Done" — causing context loss between sessions. Submodule means
one source of truth.
**Gitea credentials** for the submodule are stored in your local git config,
not in .gitmodules. If the submodule can't authenticate, run:
```bash
git config --local submodule."projects/msp-tools/guru-rmm".url \
"https://azcomputerguru:Gptf%2A77ttb123%21%40%23-git@git.azcomputerguru.com/azcomputerguru/gururmm.git"
git submodule sync
```
*No pending messages.*