Garage

Garage is a lightweight, self-hosted, S3-compatible object storage service.

Project website: https://garagehq.deuxfleurs.fr/ Source repository: https://git.deuxfleurs.fr/Deuxfleurs/garage

This Zeabur template deploys a single-node Garage instance for development, staging, and migration validation. It is not a high-availability production cluster.

What Gets Deployed

• Garage dxflrs/garage:v2.3.0
• Persistent metadata directory at /var/lib/garage/meta
• Persistent object data directory at /var/lib/garage/data
• S3 API on port 3900
• Web endpoint on port 3902
• Admin API listening inside the container on port 3903

The service starts with garage server --single-node --default-bucket, so Garage initializes a single-node layout and creates the default bucket and access key from environment variables.

Required Input

Only the public S3 API domain is required. Credentials, bucket name, internal endpoint, and service tokens are generated automatically by the template.

Default Bucket

The template creates a default bucket named vmemo-media.

Use the deployment instructions panel to copy the S3 endpoint, region, bucket, access key ID, and secret access key.

Production Note

This template uses a fixed internal RPC secret because the official Garage image does not include a shell for deriving a hex secret from Zeabur's generated password variable. The RPC port is not exposed as a public Zeabur port.

For production object storage, prefer a separate multi-node Garage cluster with at least three nodes, a generated rpc_secret, and replication_factor = 3.