S3-compatible object store for small self-hosted geo-distributed deployments
Find a file
2022-09-07 17:57:12 +02:00
doc Document available build features 2022-09-06 17:16:45 +02:00
nix Move GIT_VERSION injection later in build chain to reduce build times 2022-09-07 11:59:56 +02:00
script Fail if compiled binary is dynamic 2022-07-26 18:27:46 +02:00
src Error messages when system-libs XOR bundled-libs != 1 2022-09-07 17:57:12 +02:00
.dockerignore Build Docker image 2020-06-30 17:18:42 +02:00
.drone.yml Configure structopt to report the right version 2022-08-11 10:21:45 +02:00
.gitattributes Add FOSDEM talk and move all .pdf files to Git LFS 2022-02-16 20:01:36 +01:00
.gitignore Work on API 2020-04-28 10:18:14 +00:00
Cargo.lock Report build features in garage --help 2022-09-07 17:05:21 +02:00
Cargo.nix Report build features in garage --help 2022-09-07 17:05:21 +02:00
Cargo.toml Use the new cargo feature resolver "2" 2022-09-06 01:14:19 +02:00
default.nix Configure structopt to report the right version 2022-08-11 10:21:45 +02:00
Dockerfile Extract toolchain build from the CI 2021-10-29 11:34:01 +02:00
k2v_test.py First implementation of K2V () 2022-05-10 13:16:57 +02:00
LICENSE Switch to AGPL 2021-03-16 16:35:46 +01:00
Makefile Background task manager () 2022-07-08 13:30:26 +02:00
README.md Improve how node roles are assigned in Garage 2021-11-16 16:05:53 +01:00
rustfmt.toml Fix the Sync issue. Details: 2020-04-10 22:01:48 +02:00
shell.nix Run clippy in nix, leveraging nix caching ability 2022-07-26 18:27:52 +02:00

Garage Build Status

Garage logo

[ Website and documentation | Binary releases | Git repository | Matrix channel ]

Garage is a lightweight S3-compatible distributed object store, with the following goals:

  • As self-contained as possible
  • Easy to set up
  • Highly resilient to network failures, network latency, disk failures, sysadmin failures
  • Relatively simple
  • Made for multi-datacenter deployments

Non-goals include:

  • Extremely high performance
  • Complete implementation of the S3 API
  • Erasure coding (our replication model is simply to copy the data as is on several nodes, in different datacenters if possible)

Our main use case is to provide a distributed storage layer for small-scale self hosted services such as Deuxfleurs.