Repositories
Repositories are the core organizational unit in Paquetier. Each repository is a fully CRAN-compatible endpoint that serves R packages.
Creating a Repository
Section titled “Creating a Repository”- Navigate to Repositories in the sidebar.
- Click New Repository.
- Fill in the details:
- Slug — Used in URLs and CRAN repo paths (e.g.
my-packages). - Display Name — A human-readable name shown in the UI.
- Description — Optional description for the repository.
- Visibility — Public (accessible to anyone) or private (requires authentication).
- Slug — Used in URLs and CRAN repo paths (e.g.
- Click Create Repository.
Public vs Private Repositories
Section titled “Public vs Private Repositories”- Public repositories serve packages to anyone with the URL. No authentication is needed to install packages from R.
- Private repositories require authentication. Users must provide an API key or JWT token to access packages.
Repository Collaborators
Section titled “Repository Collaborators”Each repository has its own access control, independent of the global user role. Collaborator roles:
| Role | Permissions |
|---|---|
| Owner | Full control: manage collaborators, delete the repo, scan, upload |
| Editor | Upload packages, trigger builds |
| Viewer | Install and browse packages |
Admins can always access all repositories regardless of collaborator roles.
CRAN Endpoint
Section titled “CRAN Endpoint”Every repository exposes a CRAN-compatible endpoint at:
This URL can be used directly with install.packages() in R.
Deleting a Repository
Section titled “Deleting a Repository”Repository deletion removes the repository metadata from Paquetier but does not delete the underlying artifacts from S3 storage. Only repository owners and admins can delete repositories.