NuPaaS DocsContainer registry
NuPaaS gives every organization a private package registry, scoped to your organization and backed by the platform's own Git service. You publish scoped packages to it and consume them from your projects without publishing anything publicly.
What ships today
Find the registry at /orgs/<org>/registry. The page is feature-gated in two places — an organization-level feature exposure check and a platform rollout flag — so it may not be available to you yet even though it appears in this documentation.
Managing the registry, including rotating its token, requires an elevated org role. Members can consume packages; they cannot rotate the credential everyone else is using.
Getting your registry config
The panel hands you four things, all derived from your organization rather than configured by you:
| Parameter | Type | Description |
|---|---|---|
| registryUrl | string | The npm registry endpoint for your organization. |
| scope | string | Your package scope — the organization slug, prefixed with @. Packages you publish live under it. |
| npmrcSnippet | string | A ready-to-paste .npmrc containing the registry URL, the scope mapping and an auth token. |
| tokenName | string | A human-readable name for the token currently in use, so you can identify it later. |
Consuming packages
Copy the .npmrc snippet from the panel into your project. It maps your scope to your registry and supplies the token, which is why installs work without any further flags:
npm install @your-org/some-packagePublishing a package
Set your package's name to your scope and publish as normal. With the snippet in place, npm routes the publish to your registry rather than to the public one, because the scope mapping decides where a scoped package goes.
{
"name": "@your-org/some-package",
"version": "1.0.0"
}Published packages appear in the panel with their name, version and download URL. The list is what the registry actually holds, not a cache.
Rotating the token
Rotation issues a fresh token and returns an updated snippet. This is the right response to a token that leaked, and it should be routine when someone with registry access leaves.
Container images
There is no customer-facing container-image registry surface in the panel today. NuPaaS builds container images for you as part of a deploy and stores them itself; you do not push images by hand and there is no endpoint documented here for doing so.
If your workflow needs a specific image — a GPU job, for instance — you reference it from a registry you already control. See GPU workloads for how an image reference is supplied, and Deploy a project for how NuPaaS builds from source.