MokoGIT: Packages & Container Registry

Overview

MokoGIT includes a built-in package registry so you can publish and consume build artifacts next to your source — no separate service to run. It supports many ecosystems (npm, Composer, Maven, NuGet, PyPI, Cargo, RubyGems, Go, Helm, generic files, and more) and a Docker-compatible container registry.

Authentication

Registries authenticate with your MokoGIT access token (Settings → Applications → Generate Token). Use the token as the password for the relevant tool (npm, Composer, docker login, etc.).

npm and Composer

Point the scope or repository at your MokoGIT registry, then publish/install as usual. For example, to install a scoped npm package from MokoGIT, add to ~/.npmrc:

@yourorg:registry=https://git.mokoconsulting.tech/api/packages/YourOrg/npm/

Composer works the same way — add the MokoGIT Composer repository to your composer.json and authenticate with your token.

Container images

The container registry speaks the standard Docker/OCI protocol:

docker login git.mokoconsulting.tech
docker pull git.mokoconsulting.tech/yourorg/yourimage:latest

Public images can be pulled anonymously where sign-in gating allows it; private images require a login with your token.

Get help

Open a support ticket or call (931) 279-6313.