chore: Migrate from minio to silo (#306)

* chore: Update from minio to silo, drop in replacement

Signed-off-by: Jacob Schlecht <dadadah@echoha.us>

* docs: Add a readme note about the migration

Signed-off-by: Jacob Schlecht <dadadah@echoha.us>

---------

Signed-off-by: Jacob Schlecht <dadadah@echoha.us>

README.md

@@ -382,6 +382,13 @@ Due to an incomplete implementation, Stoat will kick any user that attempts to s
 >
 > All of your secrets can be found in `Revolt.toml` and should be copied to your `secrets.env` file. After all 5 secrets are copied over, you are safe to run `generate_config.sh` to get new configuration options.
 
+> [!IMPORTANT]
+> If you deployed Stoat before September 17th 2026 your minio environment will automatically migrate to silo. Stoat maintainers recommend backing up your minio directory. In the default configuration, this directory is at `data/minio`.
+>
+> ```bash
+> sudo cp data/minio data/minio-bak
+> ```
+
 ## Security Advisories
 
 You can find information about security advisories on Stoat repositories on Github. Listed below are the latest versions that contain remediations, and links to the security advisory pages.

compose.yml

@@ -37,7 +37,7 @@ services:
 
   # MinIO: S3-compatible storage server
   minio:
-    image: docker.io/minio/minio
+    image: docker.io/pgsty/silo
     command: server /data
     volumes:
       - ./data/minio:/data
@@ -207,7 +207,7 @@ services:
 
   # Create buckets for minio.
   createbuckets:
-    image: docker.io/minio/mc
+    image: docker.io/pgsty/mc
     depends_on:
       - minio
     entrypoint: >