S3-compatible object store for small self-hosted geo-distributed deployments https://garagehq.deuxfleurs.fr/
Find a file
Alex Auvolat af261e1789
All checks were successful
continuous-integration/drone/push Build is passing
Fix a bug when a migration is followed by a rebalance
Nodes would stabilize on different encoding formats for the values,
some having the pre-migration format and some having the post-migration
format. This would be reflected in the Merkle trees never converging
and thus having an infinite resync loop.
2022-02-10 17:38:27 +01:00
doc Small documentation updates (#237) 2022-02-10 15:58:09 +01:00
nix Generate and upload a JSON result 2022-02-05 22:09:43 +01:00
script Probably fix test-smoke 2022-02-02 17:34:19 +01:00
src Fix a bug when a migration is followed by a rebalance 2022-02-10 17:38:27 +01:00
.dockerignore Build Docker image 2020-06-30 17:18:42 +02:00
.drone.yml Remove website publishing (new website is now online) 2022-02-06 09:25:04 +01:00
.gitignore Work on API 2020-04-28 10:18:14 +00:00
Cargo.lock Support STREAMING-AWS4-HMAC-SHA256-PAYLOAD (#64) (#156) 2022-01-17 10:55:31 +01:00
Cargo.nix Support STREAMING-AWS4-HMAC-SHA256-PAYLOAD (#64) (#156) 2022-01-17 10:55:31 +01:00
Cargo.toml Skeleton to the new web API 2020-11-02 15:48:39 +01:00
default.nix Support STREAMING-AWS4-HMAC-SHA256-PAYLOAD (#64) (#156) 2022-01-17 10:55:31 +01:00
Dockerfile Extract toolchain build from the CI 2021-10-29 11:34:01 +02:00
LICENSE Switch to AGPL 2021-03-16 16:35:46 +01:00
Makefile Build Garage with Nix 2021-10-19 16:56:07 +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 Generate and upload a JSON result 2022-02-05 22:09:43 +01: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.