I love this project and I'd love to switch to it. Hopefully constructive feedback: The big issue I always run into with this stuff is what am I supposed to do if something goes wrong? I think the project documentation people would be wise to document procedures to do when certain things go wrong and how you should deal with them, such as if a server or two fail, or there's some unexpected corruption. Without that, "distributed storage" systems really feel incomplete to me. Storage is usually "mission critical" and they had a procedure for every single thing that could go wrong on the Apollo mission.

By default, it starts up exposing the file server on all interfaces, not just localhost, AKA insecure by default.

Such a poor security choice, makes me question the entire project.

It is still growing. This is not the case since many months ago.

Also, welcome to make a PR.

This is very good news, thank you!

Can you share your experience? What were the alternatives? Did you consider it against AWS S3?

Seaweed is excellent, use it in a bunch of places both big and small!

That looks awesome! What else did you try before going to SeaweedFS?

AWS EFS, MooseFS & Ceph.

Ah I've been quite happy with LizardFS (which is a fork of MooseFS) and I found Ceph to be a bit of a letdown (too complex to manage). Well, time to try Seaweed then :)