Guide: User Guide | Section: Index
Welcome to the Pantera Artifact Registry User Guide. This guide covers everything you need to know as a consumer or publisher of packages through Pantera.
- Getting Started -- What Pantera is, supported formats, repository modes, obtaining access, generating API tokens.
Step-by-step instructions for configuring your client and working with each package format:
- Maven -- Pull dependencies, deploy artifacts, configure
settings.xml. - Gradle -- Resolve dependencies and publish artifacts; aliases to the Maven family.
- npm -- Install packages, publish packages, configure
.npmrc. - Docker -- Pull images, push images, configure Docker daemon.
- PyPI -- Install packages with pip, upload with twine, configure
pip.conf. - Composer (PHP) -- Install dependencies, publish packages, configure
composer.json. - Go Modules -- Fetch modules, configure
GOPROXY. - Helm -- Add repositories, search charts, install and push charts.
- Generic Files -- Upload and download arbitrary files via curl.
- Other Formats -- RubyGems, NuGet, Debian, RPM, Conda, Conan, Hex.
- Search and Browse -- Full-text search, artifact locate, browsing via UI and HTTP.
- Cooldown -- What gets blocked and why, checking status, requesting unblock.
- Import and Migration -- Bulk import API, backfill CLI, migrating from other registries.
- JFrog Artifactory Migration -- Step-by-step guide to replace JFrog plugins with standard publishing to Pantera.
- Management UI -- Login, dashboard, repository browser, search, cooldown panel, profile management.
- Troubleshooting -- Common client-side issues and how to resolve them.
| Service | Default Port | URL Pattern |
|---|---|---|
| Repository traffic | 8080 | http://pantera-host:8080/<repo-name>/<path> |
| REST API | 8086 | http://pantera-host:8086/api/v1/... |
| Management UI | 8090 | http://pantera-host:8090/ |
| Prometheus metrics | 8087 | http://pantera-host:8087/metrics/vertx |
All package manager clients authenticate using HTTP Basic Auth where the password is a JWT token. The workflow is:
- Obtain an access token:
POST /api/v1/auth/token(returnstoken+refresh_token) - For persistent client configurations (Maven, npm, pip, Docker), use a long-lived API token:
POST /api/v1/auth/token/generate - Use your username and the token as credentials in your client configuration.
v2.1 change: All tokens are now RS256-signed. Access tokens expire after 1 hour (previously 24 hours). Use API tokens for CI/CD pipelines and tool configurations.
See Getting Started for detailed instructions.
- REST API Reference -- Complete endpoint documentation.
- Configuration Reference -- Server-side configuration options.
- Developer Guide -- Architecture and contributor information.