Overview
MokoGIT's built-in update server turns a repository's releases into a live update feed. With selectable feed formats, the feed format is chosen per repository, so the update server can speak the right protocol for each kind of software — a Joomla-style updates.xml for extensions, or an electron-updater latest.yml for desktop apps. See also MokoGIT: Releases & the Update Server.
Choosing a format
Each repository has an Update Feed Format setting (repository Settings → Update Server, or the update_feed_format field on the repo metadata REST API):
| Format | Serves | For |
|---|---|---|
off | nothing (disabled) | — |
joomla-xml | Joomla updates.xml (one signed package per stream) | Joomla extensions; recipe & manifest catalogs |
electron-yml | electron-updater latest.yml / latest-linux.yml / latest-mac.yml | Electron desktop apps (self-update) |
How the default is chosen
When the setting is left unset, MokoGIT derives the format from the repository's platform (an electron repo defaults to electron-yml; a joomla repo to joomla-xml; everything else is off). Setting the field explicitly always overrides the platform default.
Endpoints
- Joomla:
.../{owner}/{repo}/updates.xml - Electron:
.../{owner}/{repo}/updates/electron/{channel}/latest.yml
Every feed is channel-aware (dev / rc / stable) and signed, so a client only ever sees updates for the channel it follows.
Roadmap
The generator is designed so new formats are cheap to add. Planned generators give every platform a feed its own tooling understands: a Composer packages.json repository (composer require), a Go module proxy (go get), a private npm registry (npm install), a Sparkle appcast, and AppImage .zsync delta updates.
Get help
Open a support ticket or call (931) 279-6313.