MokoConsulting/wiki
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: update all .gitea/ references to .mokogitea/

Browse Source 
- ARCHITECTURE.md, Documentation-Standards, WORKFLOW_STANDARDS
- MokoWaaS build guide
- .mokogitea/ is now the standard system folder

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jonathan Miller
2026-05-11 23:38:56 -05:00
parent 0e53450e2d
commit 8ebe30f727
4 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MokoWaaS/guides-build-guide.-.-.md
+4 -4
View File
@@ -56,7 +56,7 @@ mokowaas/
│ ├── verify_changelog.sh
│ └── update_changelog.sh
│
└── .github/ (CI/CD workflows)
└── .mokogitea/ (CI/CD workflows)
└── workflows/*.yml
```
@@ -119,7 +119,7 @@ For a version to qualify as release ready:
## 6. Automated Build Options
Automated build and validation can be handled via configured CI workflows (for example, `.gitea/workflows/build.yml`) or other non-interactive tooling maintained in the repository. This keeps build behavior consistent across environments and reduces manual intervention.
Automated build and validation can be handled via configured CI workflows (for example, `.mokogitea/workflows/build.yml`) or other non-interactive tooling maintained in the repository. This keeps build behavior consistent across environments and reduces manual intervention.
Possible automations:
@@ -141,7 +141,7 @@ After release:
A continuous integration and delivery pipeline is implemented using Gitea Actions. The workflows below operationalize the build, validation, and release actions referenced throughout this guide.
### 8.1 Build and Validate Workflow (`.gitea/workflows/build.yml`)
### 8.1 Build and Validate Workflow (`.mokogitea/workflows/build.yml`)
```yaml
name: Build and Validate MokoWaaS
@@ -188,7 +188,7 @@ jobs:
path: mokowaas_ci_build.zip
```
### 8.2 Release Workflow (`.gitea/workflows/release.yml`)
### 8.2 Release Workflow (`.mokogitea/workflows/release.yml`)
```yaml
name: Release MokoWaaS
moko-platform/ARCHITECTURE.md
+1 -1
View File
@@ -161,7 +161,7 @@ All validation modules follow the pattern:
---
## Workflows (`.gitea/workflows/`)
## Workflows (`.mokogitea/workflows/`)
| Category | Purpose |
|----------|---------|
moko-platform/Documentation-Standards.-.-.md
+2 -2
View File
@@ -53,8 +53,8 @@ Every repo must have:
| `profile.ps1` | Auto-generated PowerShell profile |
| `.mcp.json` | Auto-generated MCP config |
| `.gitignore` | Git ignore rules |
| `.gitea/.moko-platform` | Repo manifest |
| `.gitea/workflows/` | CI/CD workflows |
| `.mokogitea/.moko-platform` | Repo manifest |
| `.mokogitea/workflows/` | CI/CD workflows |
## Disallowed
moko-platform/WORKFLOW_STANDARDS.md
+10 -10
View File
@@ -25,7 +25,7 @@ moko-platform-Template-Client → client-clarksvillefurs, client-ki
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
→ Copies .mokogitea/workflows/*.yml from template → target repo
```
No workflow files are stored in the API repo. This prevents drift.
@@ -153,25 +153,25 @@ To update workflows across all repos from the canonical template:
# Joomla repos -- sync from unified template
for REPO in MokoOnyx MokoCassiopeia MokoJGDPC MokoJoomHero MokoJoomTOS MokoWaaS MokoWaaSAnnounce MokoDPCalendarAPI; do
cd /a/$REPO
rm -f .gitea/workflows/*.yml
cp /a/moko-platform-Template-Joomla/.gitea/workflows/*.yml .gitea/workflows/
git add .gitea/workflows/ && git commit -m "chore: sync workflows" && git push
rm -f .mokogitea/workflows/*.yml
cp /a/moko-platform-Template-Joomla/.mokogitea/workflows/*.yml .mokogitea/workflows/
git add .mokogitea/workflows/ && git commit -m "chore: sync workflows" && git push
done
# Dolibarr repos -- sync from Dolibarr template
for REPO in MokoCRM MokoDoliForm MokoDoliAuth MokoDolibarr ...; do
cd /a/$REPO
rm -f .gitea/workflows/*.yml
cp /a/moko-platform-Template-Dolibarr/.gitea/workflows/*.yml .gitea/workflows/
git add .gitea/workflows/ && git commit -m "chore: sync workflows" && git push
rm -f .mokogitea/workflows/*.yml
cp /a/moko-platform-Template-Dolibarr/.mokogitea/workflows/*.yml .mokogitea/workflows/
git add .mokogitea/workflows/ && git commit -m "chore: sync workflows" && git push
done
# Client repos -- sync from Client template
for REPO in client-clarksvillefurs client-kiddieland; do
cd /a/$REPO
rm -f .gitea/workflows/*.yml
cp /a/moko-platform-Template-Client/.gitea/workflows/*.yml .gitea/workflows/
git add .gitea/workflows/ && git commit -m "chore: sync workflows" && git push
rm -f .mokogitea/workflows/*.yml
cp /a/moko-platform-Template-Client/.mokogitea/workflows/*.yml .mokogitea/workflows/
git add .mokogitea/workflows/ && git commit -m "chore: sync workflows" && git push
done
```