Storage Connections
Each repository in Paquetier has a dedicated storage connection that defines where its package artifacts are stored.
Storage Backends
Section titled “Storage Backends”Paquetier supports two storage backends:
S3-Compatible Storage
Section titled “S3-Compatible Storage”The primary storage backend. Works with any S3-compatible service (AWS S3, MinIO, Cloudflare R2, etc.).
Configuration options:
| Setting | Description |
|---|---|
| Endpoint | The S3 endpoint URL (e.g. s3.amazonaws.com, minio.example.com) |
| Bucket | The bucket name to use |
| Access Key | S3 access key ID |
| Secret Key | S3 secret access key |
| Region | S3 region (e.g. us-east-1) |
| Use SSL | Whether to use HTTPS for S3 connections |
| Force Proxy | Stream downloads through the server instead of using S3 presigned redirect URLs |
Storage credentials are encrypted at rest using AES-256-GCM.
Local Filesystem
Section titled “Local Filesystem”For development or small deployments, packages can be stored on the local filesystem.
Availability of this option is controlled by the PAQUETIER_LOCAL_STORAGE_POLICY setting:
all— Any authenticated user can create local storage connections.admin_only— Only admins can create local storage connections.
Creating a Storage Connection
Section titled “Creating a Storage Connection”- Navigate to Storage in the sidebar.
- Click New Connection.
- Select the storage type (S3 or Local).
- Fill in the connection details.
- Click Create.
When creating a new repository, you’ll be prompted to select or create a storage connection.
File Delivery
Section titled “File Delivery”By default, Paquetier generates S3 presigned URLs and redirects R clients directly to S3 for downloads. This reduces server load and bandwidth.
If direct S3 access is not possible (e.g. due to network restrictions), enable Force Proxy to stream files through the Paquetier server instead.