Update Server settings for repository owners (MokoGIT)

Details
Category: Reference
  • Applicable Software: MokoGIT
  • Min Version Number: 02.12 and later
  • Max Version Number: Not Applicable

Enable Update Server

The Enable Update Server master toggle turns the feed on or off for the repository. When it is off, the tab shows only the toggle and a short note — no feed is served and none of the settings below apply. Turn it on to reveal the full set of options.

Update Feed Format

The Update Feed Format controls the document that MokoGIT publishes for consumers:

  • Default (from platform) — use the format the platform picks for the repository. This is the recommended default.
  • Off — do not publish a feed document even though the Update Server is enabled.
  • Joomla XML — publish a Joomla extension update feed (updates.xml style), for Joomla extensions.
  • Electron YML — publish an Electron auto-updater feed (latest.yml style), for Electron desktop apps.

Feed Visibility

Feed Visibility is a single control that governs who can reach the feed and what it exposes:

  • Public — the feed lists versions and serves downloads. Anyone who can reach the URL can check for and download updates.
  • No downloads — the feed lists versions only. Consumers can see that a new version exists, but the download links are not served.
  • Hidden — the feed is not served at all; requests return 404. Use this to keep a repository's feed private without disabling the Update Server.
  • Require license key — the feed is gated behind a valid license key. Consumers must present a valid key to see versions and download updates.

Note: Feed access is now controlled entirely by Feed Visibility. The previous standalone Require license key checkbox has been retired and folded into this dropdown as the Require license key option.

Download Gating

Download Gating decides which releases are downloadable through the feed:

  • None — no gating; all published releases are downloadable (subject to Feed Visibility).
  • Pre-release only — gate only pre-release builds, while stable releases stay downloadable.
  • All — gate every release behind the download rules.

Branch → Update Stream mapping

The Branch → Update Stream mapping ties each repository branch to an update stream (channel) that consumers subscribe to. For example, you can map your stable branch to a stable stream and a testing branch to a beta/pre-release stream, so consumers on each channel receive only the releases built from the matching branch.

Summary

  • Enable Update Server — master on/off for the repository feed.
  • Update Feed Format — Default (from platform) / Off / Joomla XML / Electron YML.
  • Feed Visibility — Public / No downloads / Hidden (404) / Require license key.
  • Download Gating — None / Pre-release only / All.
  • Branch → Update Stream — map branches to release channels.
Hits: 33