From Artifactory or Nexus
Artifactory and Nexus Repository are multi-format repository managers. Both offer hosted, proxy, and aggregate repository types for PyPI. peryx covers the same repository shapes for the ecosystems listed under Ecosystems.
Peryx differences
Nexus 3.93 added PEP 658 and PEP 691, and 3.94 added PEP 700. Artifactory supports the Simple JSON API when an administrator enables JSON indexing. peryx serves PEP 658, PEP 691, and PEP 700 without a feature switch and synthesizes core metadata when an upstream does not provide it.
Artifactory permission targets and Nexus
access control bind users or groups to repository permissions. Peryx
role grants authorize management operations. Artifact clients use
configured access grants or managed scoped tokens
for read, write, and delete actions.
Check the current product documentation before translating Artifactory LDAP, Nexus authentication, Artifactory HA, Nexus HA, Artifactory cleanup, or Nexus cleanup. Editions and deployment requirements differ.
Configuration mapping
| Artifactory / Nexus | peryx |
|---|---|
| remote / proxy repository | cached index |
| local / hosted repository | hosted index |
| virtual / group repository | virtual index |
…/api/pypi/{repo}/simple (Artifactory) | /{route}/simple/ |
…/repository/{repo}/simple (Nexus) | /{route}/simple/ |
| deploy through the UI, REST API, or a client | twine upload or uv publish |
| repository permissions, roles, and users | role grants for management; configured or managed scoped tokens for artifact clients |
| directory or OIDC identity | LDAP or OIDC login with group-to-role mappings |
| HA deployment | [availability] with dc or ha |
| scheduled cleanup policy | retention plan preview and export |
Pitfalls
- Keep repositories for ecosystems that peryx does not serve in their existing manager.
- Peryx LDAP and OIDC identities govern management and UI access. They do not replace the scoped credentials used by
pip,uv, andtwinefor artifact requests. - Artifactory and Nexus can execute scheduled cleanup policies. Peryx retention evaluates and exports a read-only plan; it does not apply that plan or schedule deletion.
- Preserve virtual-repository ordering. Map path-specific include or exclude rules to separate peryx routes when layer order is not enough.