MokoConsulting/MokoCLI
Public Access
1
0
Fork 0
Code Issues 3 Pull Requests Packages Releases 8 Wiki Activity

docs: update architecture section — sync engine clones templates at runtime

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jonathan Miller
2026-05-02 18:18:23 -05:00
parent 2bfbc2d89d
commit 06b1a36320
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/WORKFLOW_STANDARDS.md
+12 -1
View File
@@ -13,7 +13,18 @@ MokoStandards-Template-Generic → MokoISOUpdatePortable, etc.
MokoStandards-Template-Client → client-clarksvillefurs, client-kiddieland
```
**MokoOnyx** is the living reference implementation for Joomla workflows. Template repos are the canonical source for distribution. The MokoStandards-API repo does NOT store workflow templates — it only has `bulk-repo-sync.yml` for its own CI.
**MokoOnyx** is the living reference implementation for Joomla workflows. Template repos are the **single source of truth** for workflow content. The MokoStandards-API repo does NOT store workflow templates — its sync engine (`RepositorySynchronizer.php`) clones template repos at runtime to get the latest workflows.
### How Sync Works
```
bulk-repo-sync.yml (API repo)
→ RepositorySynchronizer.php detects platform type
→ Clones the matching template repo to /tmp/
→ Copies .gitea/workflows/*.yml from template → target repo
```
No workflow files are stored in the API repo. This prevents drift.
## Template Repos