Formats overview
Each page in this section covers one format: how to set up hosted, proxy and group repositories, how to configure the native clients, how to publish, and what to check when something fails.
| Format | Hosted | Proxy | Group | Client URL |
|---|---|---|---|---|
| Raw | ✅ | ✅ | ✅ | https://entrepot.example.com/repository/<name>/ |
| PyPI | ✅ | ✅ | ✅ | https://entrepot.example.com/repository/<name>/simple/ (index), …/<name>/ (upload) |
| npm | ✅ | ✅ | ✅ | https://entrepot.example.com/repository/<name>/ |
| Docker / OCI | ✅ | ✅ | ✅ | entrepot.example.com/<name>/<image> |
| Apt | ✅ | ✅ | — | https://entrepot.example.com/repository/<name> |
| Yum | ✅ | ✅ | — | https://entrepot.example.com/repository/<name>/ |
| Helm | ✅ | ✅ | ✅ | https://entrepot.example.com/repository/<name>/ |
The UI’s Set up client panel on each repository page shows the snippets below pre-filled for that repository, both for a workstation (Local) and for a GitLab CI job.
Credentials
Section titled “Credentials”Every client authenticates with a token:
- an Entrepot API token (
ent_…) — personal (API tokens in the UI) or a service-account token, - an OIDC access token from your identity provider,
- a GitLab CI/CD
id_token.
Send it as Authorization: Bearer <token>, or — wherever a client wants a
username and password — as the password with any username. The docs
use token, __token__ or gitlab-ci as the username purely for
readability.
Repositories with anonymousRead: true can be read without credentials; you
still need a token to publish.
Common responses
Section titled “Common responses”| Status | Meaning |
|---|---|
401 |
No credentials, or credentials that are invalid or expired. Invalid credentials are never downgraded to anonymous access. |
403 |
Authenticated, but the role bindings don’t allow the action (… is not permitted to write npm-internal), or the component is quarantined (header X-Entrepot-Quarantined: true). |
404 |
Not found — or a routing rule blocked the name from being fetched upstream. |
409 |
The file or version already exists and the hosted repository doesn’t allow redeploys. |
502 |
A proxy couldn’t reach its upstream and had nothing cached. |
Uploading through the API
Section titled “Uploading through the API”Besides the native clients, every hosted repository accepts a multipart upload through the management API, which is handy for scripts and the UI:
curl -fsS -H "Authorization: Bearer $ENTREPOT_TOKEN" \ -F file=@dist/mypkg-1.0.0-py3-none-any.whl \ https://entrepot.example.com/api/v1/repositories/pypi-internal/uploadExtra form fields: path (raw: destination path; yum: directory),
distribution and component (apt), tag (npm dist-tag, default
latest). See the API recipes.