Being new to the world of DevOps and day by day discovering the most used tools, I met the excellent MINIO S3, widely used by more than one.
Unfortunately I only became aware of it at a time when it was no longer completely free. Which, according to everything I have read, has led the majority to turn to other alternatives including SeaweedFs (despite the existence of Fork versions of Minio).
Having been seduced by “the fairly convincing performances described on the internet of SeaweedFs (especially on its Github page)”, and having decided to test it, I very quickly realized that it will be necessary to read a lot before arriving at an ideal configuration as a starting point. So it took me a while to get the gist of it.
I therefore grouped my research and configuration experiences into a short guide that I thought I would share here (through a Github link) in order to collect advice and opinions from the community (senior-junior-experts etc.) to help improve it so that it can help (for rapid deployment) others who would like to use it as an alternative to Minio S3.
<a href="https://github.com/delacosta456/technical-guides/wiki/A-typical-step%E2%80%90by%E2%80%90step-example-of-SeaweedFS-HA-Setup-Guide-%E2%80%94-3-VMs---1-Postgres-metadata-store-on-docker-hosted-on-separate-VM" target="_blank" rel="noopener nofollow">READ IT ON GITHUB</a>

delacosta456

A junior developer shares their experience setting up SeaweedFS as a self-hosted, open-source alternative to MinIO S3. After discovering MinIO's licensing changes, they explored SeaweedFS and compiled a step-by-step guide for a high-availability setup using 3 VMs with a PostgreSQL metadata store running on Docker. The guide is shared on GitHub to gather community feedback and help others get started quickly.

Sharing Junior Dev experience with SeaweedFs: IMHO one of Minio's alternatives to consider