fix: force HTTPS S3 endpoint to avoid Coolify 307 on uploads

http://s3 hosts redirect to https; AWS SDK cannot follow PUT redirects, which caused XML parse errors.

.env.example

@@ -27,14 +27,18 @@ S3_ACCESS_KEY=minioadmin
 S3_SECRET_KEY=minioadmin
 
 # SeaweedFS live example (preferred aliases also work without S3_*):
-# Use the public HTTPS URL (SERVICE_URL_S3). Port 8333 is often internal-only.
+# Use the public HTTPS URL (SERVICE_URL_S3). Never use plain http:// for the public host —
+# Coolify/Traefik returns HTTP 307 and AWS SDK PutObject cannot follow it.
+# Do NOT use :8333 from outside the SeaweedFS network (often refused).
 # S3_ENDPOINT=https://s3.game-no.ir
 # SERVICE_URL_S3=https://s3.game-no.ir
-# SERVICE_URL_S3_8333=https://s3.game-no.ir:8333
 # SERVICE_USER_S3=...
 # SERVICE_PASSWORD_S3=...
 # AWS_ACCESS_KEY_ID=${SERVICE_USER_S3}
 # AWS_SECRET_ACCESS_KEY=${SERVICE_PASSWORD_S3}
+#
+# File uploads: multer uses MEMORY storage and streams the buffer straight to the
+# S3 temp bucket. No Coolify persistent volume / uploads folder is required for this.
 
 S3_TEMP_BUCKET=temp
 S3_CERTIFICATES_BUCKET=certificates