101–110 of 112 posts
Garage 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/
Earlier quoted context omitted.
The trouble I had with SeaweedFS was that the docs I found were rather sparse. Garage, on the other hand seemed pretty well documented.
Did you miss the wiki or was the wiki not enough? Please let me know. I work on SeaweedFS.
Is there any "local"/minio-esque object store properly implements the full conditional GET/PUT/DELETE spec, ETag, etc.? I have struggled to find this in the past.
I implemented this (HS5). Etags match the AWS S3 ones as well.
Earlier quoted context omitted.
Because if you ship a tool with s3 support, the customer can decide if he wants to store in the cloud, or spin up a docker container locally.
The same argument can be made for the other side: the customer can also trivially mount the S3 bucket as a filesystem, if you decide to ship the tool with filesystem support instead.
But is that really something you do in an enterprise application?
What if you write a file with the same name from two servers to the bucket? What about latency? What if the connection / mount fails, how would the application even notice?
Never tried it, I don't think it fits our needs.
Running Sentry on prem, I had to swap out their default SeaweedFS setup for Garage because the former kept failing under concurrent writes. I tried digging around for a bit, but found that the swap was easier and faster, Garage has also worked great for single node use cases (e.g. tested up to around 10 TB of data). I still think that SeaweedFS is a cool project, might have been a config issue or something, wasn’t wo…
SeaweedFS performance should be the fastest. Please create an issue if there are any performance issues with SeaweedFS, or you see it is slower than any alternatives. (I work on SeaweedFS)
Do you have plans to improve the docs? Some of the info I needed was inside GitHub issues / discussions.
Overall very cool project. One of these days I'll reach out about enterprise support for my usecase.
A notable mention should also be Versity GW, https://github.com/versity/versitygw/
I'm quite pleased with it. It's also nice that it translates directly to the file system .
On the other hand, this means that it's bound by filesystem naming rules - e.g. you can't have an object named "abc/", or a pair of objects named "a" and "a/b".
Really happy with my own https://deltaglider.com/ - Filesystem backend - Encrypted S3 backend - Compressed S3 backend (Saving a ton of money here) - Cross backend replication - Full IAM - Full GUI with OIDC auth
- slop code [0] - slop copy [1] [0] https://github.com/beshu-tech/deltaglider_proxy/graphs/contr... [1] https://deltaglider.com/pricing/
I made it explicit Deltaglider was created by SWEs, aided by Fable 5.x.
Also, I asked Fable to un-slop the copy of the website, using this excellent skill https://github.com/blader/humanizer
Check it out, once again: https://deltaglider.com/
Earlier quoted context omitted.
If it's open source, you don't do daily pulls and you have a competent AI to crawl the codebase; why does it matter the ethnicity at this point?
Ethnicity never mattered (other than for the people that think too many white people are doing something). It's culture, in particular government ties, that are the worry with China.
Earlier quoted context omitted.
SeaweedFS performance should be the fastest. Please create an issue if there are any performance issues with SeaweedFS, or you see it is slower than any alternatives. (I work on SeaweedFS)
I've been watching seaweedfs for a few years now. It is very cool tech and I'm itching to use it but unfortunately the docs are very bare bones. Do you have plans to improve the docs? Some of the info I needed was inside GitHub issues / discussions. Overall very cool project. One of these days I'll reach out about enterprise support for my usecase.