Migration

Coming from another Python index, mapped to peryx.

• From devpi

  What devpi and peryx share, what devpi does that peryx does not, what peryx adds, and how to move across.

• From proxpi

  What proxpi and peryx share, where proxpi stays minimal, what peryx adds, and the one-line client change to move.

• From pypiserver

  What pypiserver and peryx share, why its fallback redirect is not a cache, what peryx adds, and how to move.

• From pypicloud

  What pypicloud and peryx share, the cloud backends it offers, what peryx adds, and how to move off an archived project.

• From simpleindex

  Route-per-project becomes virtual layers, and the redirects become a cache.

• From Artifactory or Nexus

  Keep them for the other ecosystems if you must; serve Python from one small binary with the modern protocols first.

• From cloud registries

  CodeArtifact, GitLab, Azure Artifacts, and Google Artifact Registry: what their Python support misses, and how peryx fronts or replaces them.

• From bandersnatch

  A mirror of everything versus a cache of what you use: when the full copy stops paying for its terabytes.

• From Pulp

  pulp_python covers the same ground with a platform's machinery; peryx is the same ground as one process.

• From static and legacy setups

  dumb-pypi, --find-links directories, pip2pi, nginx caches, and the other duct tape, mapped to one server.