Your builds depend on the public internet: PyPI, npm, crates.io, ConanCenter, Docker Hub, distribution mirrors. When one of them is slow, down, rate-limited or quietly changes a file, your builds feel it. Depotify puts a repository you control between your teams and the outside world.

Three kinds of repository

KindWhat it isTypical use
Hostedholds what your teams uploadyour own packages, images and files
Remotea cache of an upstream repository, filled on demandPyPI, npm, Docker Hub, a distribution mirror
Virtualone address in front of several hosted and remote repositorieswhat developers and build servers actually point at

The type is chosen when a repository is created, in the same dialog for every tool, and every option says what it allows and what it refuses — recommendations are only defaults.

Creating a remote repository: every option says what it allows
Creating a remote repository: every option says what it allows

Remote repositories: a cache with rules

  • On demand. The first request fetches from upstream and keeps the file; every later one is served locally. A remote can also fetch ahead in the background, at a pace you set, and stops before the disk fills.
  • Fresh enough, not too fresh. How long index data is trusted, how long a "not found" is remembered, and whether the repository runs offline are set per repository, per tool, or for the whole site.
  • Offline is a feature. In offline mode — or when the upstream is down — cached content keeps being served, and what is not cached is refused with a clear reason instead of a hang.
  • Fetching is a right. Who may cause a download from the internet is a rule of its own; others get only what is already cached.
  • Checked on the way in. Hashes are verified where the upstream provides them, PyPI metadata is checked, and RPM and Debian upstreams can have their signatures verified — and the index re-signed with your own key.
  • Held for review. Fetched files can be held until someone approves them, before anyone can install them. See Access control.
  • No loops. A repository never fetches from itself, directly or round a chain of servers; a configuration change that would create a loop is refused.

Virtual repositories: one address

A virtual repository merges its members into one view: one pip index URL, one npm registry, one Maven repository, one Docker registry address.

  • Local wins. When your own package and a public one share a name, yours is served — the defence against dependency-confusion attacks is the default, not a setting. Each tool decides what "the same package" means in its ecosystem: a project name, a scope, a version.
  • Uploads go to one member you name; a virtual repository without one refuses uploads rather than guessing.
  • Members keep their rules. By default, reading through a virtual repository needs the right to read it and the member. To publish a private member's content through a public virtual repository, the administrator marks it exposed: its files are then served under the virtual repository's rules, while the member itself stays invisible and closed — its name is not even revealed. Exposing never grants write or delete, and never skips a security review.
  • Signed for RPM and Debian. A virtual RPM or Debian repository publishes one merged index, signed with your key.

Connections: upstreams, entered once

Addresses, accounts, tokens and certificate authorities of upstream servers are entered once, in a catalogue of named connections, and chosen by name wherever they are needed. Renewing a token is one change, not twenty.

  • Secrets are stored encrypted and never shown again.
  • Credentials are sent only to the server they belong to — a redirect to another host does not take them along.
  • Each tool's rule administrators manage its connections.

A catalogue of upstreams

Depotify ships a catalogue of ready-made remote repositories and mirrors — AlmaLinux, Debian, PyPI, npm, crates.io, ConanCenter, Docker Hub, GitHub and more — organised by tool and group. Adding one opens the tool's own dialog already filled in, including the connection it needs. The catalogue updates itself from its source and lists only the tools the site runs.

The catalogue of upstreams, by family and tool
The catalogue of upstreams, by family and tool

Mirrors for version control

git, Mercurial and Subversion repositories can mirror an upstream repository: read-only, synced on a schedule or on demand, with a history of every sync. A mirror can be detached to become a normal repository of its own — the usual way to take over a project you depend on.