← Back to Home
Universal Update Server Standard
Canonical reference for the update server architecture across all Moko Consulting repositories.
Overview
All Moko Consulting repositories use a universal update server pattern based on the Joomla update XML format. This provides a consistent way to track versions, stability channels, and download URLs across all platforms (Joomla, Dolibarr, generic, MCP, Node.js).
The .mokogitea/manifest.xml file in each repository determines how the update server data is interpreted for that platform.
Stability Channels
| Channel |
Tag |
Suffix |
Trigger |
| Stable |
stable |
(none) |
PR merge to main |
| Release Candidate |
release-candidate |
-rc |
Draft PR to main |
| Beta |
beta |
-beta |
Manual dispatch |
| Alpha |
alpha |
-alpha |
Manual dispatch |
| Development |
development |
-dev |
Feature merge to dev |
CLI Tools
| Tool |
Purpose |
updates_xml_build.php |
Build/update updates.xml |
release_package.php |
Build ZIP/tar.gz, upload assets |
release_create.php |
Create/overwrite Gitea releases |
release_promote.php |
Promote between channels |
release_cascade.php |
Delete lesser channels |
release_mirror.php |
Mirror to GitHub |
manifest_element.php |
Extract element/type/prefix |
Workflows
| Workflow |
Purpose |
auto-release.yml |
Build and release on PR merge to main |
pre-release.yml |
Dev/alpha/beta/RC pre-releases |
update-server.yml |
Update server management |
All workflows source from Template-Generic and sync to all template and governed repos.
See moko-platform wiki UPDATE_SERVER for full documentation.