MokoGIT

MokoGIT is your private, fully managed Git hosting service powered by Gitea. Manage repositories, CI/CD pipelines, issues, and wiki documentation.

Read more →

🚀 MokoGIT Roadmap – See What’s Coming Next!

Details
Category: MokoGIT
  • Applicable Software: MokoGIT
  • Min Version Number: 02.65.00
  • Max Version Number: Not Applicable

MokoGIT is our self-hosted Git platform — repositories, pull requests, releases, CI/CD, package registries, org-wide governance and native Joomla update-server generation, all in one place. The roadmap below shows what we have recently shipped and what is coming next.

MokoGIT Roadmap (current stable 02.65.00)

  • Auto-finalize that self-heals an interrupted release merge.
  • Auto-dispatch to self-heal a missing release run.
  • Orphan release and asset auditor with optional cleanup.
  • Governance drift auditor that detects and can re-apply branch-protection drift.
  • Release and version drift auditor flagging tag-to-release mismatches.
  • Sync-profile drift alerter surfacing stuck profiles.
  • Dispatch-stall watchdog to catch release-queue starvation.
  • Automatic re-provisioning of a missing release-candidate branch.

  • Teams as permission groups — granular org-level and site-level role-based access control.
  • First-class org-level cascade governance for release branches.
  • A customizable browser-based web console (shell) for MokoGIT.
  • Per-rule enable/disable for branch-protection rules without deleting them.
  • Release-packaging and sync-profile reliability fixes.

  • Custom repository roles and scoped site-level roles beyond simple admin.
  • Org-admin capability delegation to teams.
  • Admin "Run next" to manually prioritise a queued workflow run.
  • Org-wide webhooks page listing every repo's webhooks in one view.
  • Multi-select releases and tags with bulk actions.
  • A fuller Git org-capability REST surface plus matching MCP tools.

  • Deeper self-healing automation across the whole release and governance pipeline.
  • Expanded Joomla update-server tooling for the full Mokonyx fleet.

Items and timing are indicative and may change based on feedback and feasibility.

Hits: 2

Getting Started: Your Account and First Repository

Details
Category: Getting Started
  • Applicable Software: MokoGIT
  • Min Version Number: 02.08.00
  • Max Version Number: Not Applicable

Logging In

Your MokoGIT account is created by your Moko Consulting administrator. To log in:

  1. Navigate to your MokoGIT instance URL (provided by your administrator).
  2. Enter your username and password.
  3. Click Sign In.

If you've forgotten your password, use the Forgot Password link on the login page, or contact your administrator.

Hits: 147

Read more …

What is MokoGIT?

Details
Category: Getting Started
  • Applicable Software: MokoGIT
  • Min Version Number: 02.08.00
  • Max Version Number: Not Applicable

Overview

MokoGIT is a private, self-hosted Git service powered by Gitea — a lightweight, open-source platform similar to GitHub or GitLab. Provided and fully managed by Moko Consulting, MokoGIT gives your team a secure, dedicated instance for hosting code without the hassle of server setup or maintenance.

Hits: 100

Read more …

MokoGIT: License Management (Commercial Licensing)

Details
Category: Guides
  • Applicable Software: MokoGIT
  • Min Version Number: 02.00.00
  • Max Version Number: Not Applicable

MokoGIT includes a built-in commercial license management system for organizations that sell extensions or applications (Joomla, Dolibarr, Electron apps, and more). It handles license-key generation, validation, update-feed gating, domain enforcement, and payment-system integration — so you can license and deliver paid software straight from your repositories.

Two levels

  • Organization — packages and keys shared across every repo in the org (/{org}/-/licenses).
  • Repository — the same, scoped to one repo, plus per-repo update-feed URLs (/{owner}/{repo}/licenses).

License packages

A package defines a subscription tier (for example “Pro Annual” or “Basic Monthly”):

  • Duration — key validity in days (0 = lifetime).
  • Max sites — maximum unique domains a key may activate (0 = unlimited).
  • Channels — which update streams the package grants access to.
  • Active — whether the package is currently sold.

Every org/repo also gets a protected Master (Internal) package with an internal key — unlimited access to all channels; it can be revoked but not edited or deleted.

License keys

  • Keys look like MOKO-XXXX-XXXX-XXXX-XXXX and are hashed (SHA-256) before storage — the full key is shown once at creation, so store it securely.
  • Each key can carry a licensee name/email, a domain restriction, a max-sites override, and a custom expiry date.

Gating downloads

License keys tie into the Update Server: set a repository's Feed Visibility to Require license key and consumers must present a valid key to list versions and download updates. Domain and channel access are checked at validation time.

Selling & automation (API)

  • Purchase webhook — POST /api/v1/repos/{owner}/{repo}/license-keys/purchase creates a key from a payment event (Stripe, PayPal, etc.). A payment_ref makes it idempotent, so a retried webhook returns the existing key instead of creating a duplicate.
  • Validation — the public POST .../license-keys/validate endpoint checks a key + domain for client-side license checks.
  • Admin endpoints (token + repo admin) manage packages and keys — list, create, edit, delete, and view usage logs.

Where to manage it

  • Repository: {owner}/{repo} → Licenses.
  • Organization: {org} → Licenses (shared across all repos in the org).

Get help

Open a support ticket or call (931) 820-0265.

Hits: 55

MokoGIT: Custom Issue Statuses, Priorities & Types

Details
Category: Guides
  • Applicable Software: MokoGIT
  • Min Version Number: 02.00.00
  • Max Version Number: Not Applicable

MokoGIT extends the built-in issue tracker with organization-level custom issue metadata — Statuses, Priorities, and Types that every repository in the org shares. Unlike plain labels, these are first-class fields with their own definitions, colors, defaults, and (optionally) required-on-create enforcement.

Custom Statuses

  • Each org defines its own issue statuses (for example In Progress, Blocked, Pending: Review, Resolved), each with a color and a closes-issue flag — applying a closes-issue status closes the issue.
  • Presets seed a standard status set into an org in one step, and a protected baseline keeps core statuses from being removed.

Priorities

  • Org-defined priorities (for example Critical / High / Medium / Low), each with a color; one is marked the default applied to new issues.

Types

  • Org-defined issue types (for example Bug, Feature, Enhancement, Task, Documentation, Security, Infrastructure), each with a color; one is the default.

Required on create

An organization can require that every new issue carry a Status, Priority, and Type. When enforced, creating an issue without them is rejected — so issues are triaged consistently across the org's repositories from the moment they're opened.

Where to set it

  • Org-wide: organization Settings → Issue Statuses / Priorities / Types. The same definitions are available over the REST API (and the MokoGIT MCP server) for automation.
  • Per issue: choose the Status, Priority, and Type when creating or editing an issue.

Get help

Open a support ticket or call (931) 820-0265.

Hits: 30
  1. MokoGIT: Update Feed Formats
  2. MokoGIT: Cascade Merge Rules
  3. MokoGIT: CI/CD & Release Pipeline
  4. MokoGIT: Branch Model & Release Channels

Subcategories

Getting Started

Guides

Troubleshooting