Ravenstash key concepts
Ravenstash organizes private content like this:
account or organization → namespace → repository → registry type ├─ package → version → file └─ OCI repository → tag/digest → manifest/blob/referrer| Term | Meaning |
|---|---|
| User | One signed-in person. |
| Owner | The personal account or organization that owns a repository and its automation tokens. |
| Organization | A group of users with shared namespaces, repositories, and tokens. Organization administrators have full access everywhere; members work in the namespaces they belong to. Membership does not replace a user’s personal account. |
| Namespace | A group of repositories inside a personal account or organization. In an organization, it is also a membership boundary: people work only in namespaces they belong to. Every owner has a default namespace. |
| Repository | A private package and artifact space inside a namespace. It can support one or more registry types. |
| Namespace member | An organization member who belongs to a namespace, because they were added or invited, joined automatically, belong to an attached organization Team, or administer it. |
| Team | A reusable group of organization members. An organization Team is attached to some or every namespace; a namespace Team stays inside one namespace. |
| Repository role | A named set of repository permissions: Reader, Publisher, Maintainer, Admin, or an organization’s custom role. |
| Grant | A repository role given to a Team or a namespace member on every repository in a namespace or on specific repositories. Organization Teams can also receive a role on every repository in the organization. Grants combine additively. |
| Base permission | The role every member of a namespace receives on its current and future repositories. Each namespace has its own. |
| Registry type | PyPI, npm, Maven, or OCI support within a repository. Each keeps its familiar package format, URL, and tools. |
| Package / version / file | A PyPI, npm, or Maven package groups versions; a version contains one or more package files. |
| OCI repository / tag / digest | A Container or Helm OCI repository groups manifests and blobs. Tags are mutable selectors; digests are immutable identities. |
| API token | An automation credential used by rvs in CI and release jobs. It can access repositories owned by the same owner. |
| Private mirror | A private read-only mirror of a public or authenticated package source. Use it directly or connect it to a private repository. |
| Upstream | A source connected to a PyPI, npm, or Maven repository on its Upstreams tab: a private mirror or another private repository. Upstreams are checked in order after the repository’s own packages. See Upstreams and private mirrors. |
| Package resolution rule | A setting on a repository’s Rules tab that chooses which upstreams can supply the packages it matches, and whether versions can come from several sources. See Package resolution rules. |
| Package storage | Where private package files are stored: managed North America, European Union, or eligible customer-owned storage. Custom package caches inherit the customer managed default when created. Storage location is separate from worldwide package delivery. |
How package formats fit into a repository
Section titled “How package formats fit into a repository”All enabled registry types share the repository owner, namespace, name, and storage choice. Each keeps its familiar package format and URL.
For example:
https://pypi.rvsta.sh/platform/releases/simple/https://npm.rvsta.sh/platform/releases/https://maven.rvsta.sh/platform/releases/oci.rvsta.sh/platform/releases/acme/api:1.0.0Addresses that use a name-based target change when a namespace or repository is renamed. Ravenstash also provides ID-based targets made from permanent IDs for long-lived integrations. See Repository names and addresses, Multiple ecosystems in one repository, and Organizations and access for details.