Reference
Branding your MokoGIT instance (logo, favicon, and the one-SVG generator)
- Details
- Category: Reference
- Applicable Software: MokoGIT
- Min Version Number: 02.21.00 and later
- Max Version Number: Not Applicable
Overview
MokoGIT ships fully MokoGIT-branded out of the box. An instance administrator can re-brand it from Site Administration → Branding (/-/admin/branding). Branding is configured entirely in the web UI (it is intentionally not exposed in the REST API).
- Hits: 39
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
MokoGIT can serve an update feed for a repository so that installed extensions or applications can discover and download new versions automatically. You configure this per repository under Settings → Update Server. This guide explains each setting for repository owners.
- Hits: 33
Managing your MokoGIT API keys (access tokens)
- Details
- Category: Reference
- Applicable Software: MokoGIT
- Min Version Number: 02.22.00 and later
- Max Version Number: Not Applicable
What are access tokens (API keys)?
A personal access token is a secret key that lets scripts, tools, and integrations act on your behalf on MokoGIT without using your password. You use tokens for things like Git over HTTPS, CI jobs, the API, and MCP clients. Each token can be limited to only the permissions (scopes) it needs, and can be revoked at any time without affecting your password or other tokens.
Treat a token like a password. It is shown only once, at creation. Copy it immediately and store it in a secret manager. MokoGIT keeps only a hashed form and cannot show it to you again.
- Hits: 39