Alternatives to MinIO for single-node local S3
1–10 of 112 posts
Re: Alternatives to MinIO for single-node local S3
#2Just use the damn file system. Why does everyone have to put HTTP between everything?
Re: Alternatives to MinIO for single-node local S3
#3Garage added an automatic configuration feature in v2.3.0 that makes it easier to set up single nodes:
garage server --single-node --default-bucket
https://garagehq.deuxfleurs.fr/documentation/quick-start/Re: Alternatives to MinIO for single-node local S3
#4One alternative worth looking at is S2: https://github.com/mojatter/s2
Re: Alternatives to MinIO for single-node local S3
#5Rustfs, works pretty well for me
Re: Alternatives to MinIO for single-node local S3
#6Just use the damn file system. Why does everyone have to put HTTP between everything?
Because you might be running something that only talks S3 and want to point it at something local.
Re: Alternatives to MinIO for single-node local S3
#7or rclone serve
Re: Alternatives to MinIO for single-node local S3
#8Just use the damn file system. Why does everyone have to put HTTP between everything?
Because you want to mock the tools you are going to use in production locally or in CI. Really good reasons to not totally change what you are doing in your app between environments.
Re: Alternatives to MinIO for single-node local S3
#9Just use the damn file system. Why does everyone have to put HTTP between everything?
Because this is about having a local standin for S3, which (in a production deploy) often solves a different problem than a (local) filesystem.
This post does not even mention the S3 API as a replacement for a filesystem.
Re: Alternatives to MinIO for single-node local S3
#10For single-node local S3, I often just use `s3fs` mounting a local directory. MinIO always felt like overkill for simple dev.