Overview
MokoGIT turns a repository’s releases into live update feeds that installed software can check automatically. Cut a release once, and MokoGIT can advertise it to Joomla, WordPress, PrestaShop, Drupal, and Composer clients — optionally gated behind a valid license for commercial products.
Cutting a release
- Tag a version and publish a Release (with notes and attached build artifacts) from the repository’s Releases tab, or automatically from your CI pipeline.
- MokoGIT follows a dev → rc → stable promotion ladder: changes are validated on development, staged for release-candidate testing, then promoted to a stable release.
The update server
For each repository you can enable an update stream that generates the correct feed format for the target platform from that repo’s releases:
- Joomla update XML, WordPress/PrestaShop/Drupal update endpoints, and Composer package metadata.
- Feed access is governed by the per-repo update-stream config (enabled flag, download-gating, license/download key), so a feed can serve regardless of repository visibility — it is not tied to repo membership.
- A flagship allowlist gates the public stable channel: only allow-listed repositories advertise a real stable stream; everything else is presented on the development channel with a “not certified stable” note, so uncertified extensions never ship a stable update.
Gated downloads (DLID licensing)
Commercial releases can be license-gated: the download is delivered only after a valid license is validated, using a non-secret DLID download identifier in the update URL and ed25519-signed download links. Public / open-source products stay ungated and download normally. For the license side of this (activation, seats, allotments), see the MokoOnyx Licensing help section.
Get help
Open a support ticket or call (931) 279-6313.