S3-compatible object store for small self-hosted geo-distributed deployments
Find a file
trinity-1686a 60d4459926 BucketWebsite (#174)
fix #77

this does not store anything but a on/off switch for website, and does not implement GetBucketWebsite as it would require storing more. GetBucketWebsite should be pretty easy to implement once data is stored though.

Co-authored-by: Trinity Pointard <trinity.pointard@gmail.com>
Reviewed-on: https://git.deuxfleurs.fr/Deuxfleurs/garage/pulls/174
Co-authored-by: trinity-1686a <trinity.pointard@gmail.com>
Co-committed-by: trinity-1686a <trinity.pointard@gmail.com>
2021-12-15 10:41:39 +01:00
doc Add a second plot 2021-12-13 11:58:03 +01:00
nix Extract toolchain build from the CI 2021-10-29 11:34:01 +02:00
script In ListBuckets, hide entry if no perms 2021-11-22 12:10:28 +01:00
src BucketWebsite (#174) 2021-12-15 10:41:39 +01:00
.dockerignore Build Docker image 2020-06-30 17:18:42 +02:00
.drone.yml Extract toolchain build from the CI 2021-10-29 11:34:01 +02:00
.gitignore Work on API 2020-04-28 10:18:14 +00:00
Cargo.lock Improve how node roles are assigned in Garage 2021-11-16 16:05:53 +01:00
Cargo.nix Improve how node roles are assigned in Garage 2021-11-16 16:05:53 +01:00
Cargo.toml Skeleton to the new web API 2020-11-02 15:48:39 +01:00
default.nix Use Rust binaries from Nix instead of rustup 2021-10-29 11:34:01 +02: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 Extract toolchain build from the CI 2021-10-29 11:34:01 +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.