fix: avoid failing mc cors setup in minio-init

- configure CORS via MINIO_API_CORS_ALLOW_ORIGIN

- keep minio-init responsible only for bucket creation

docker-compose.yml

@@ -76,6 +76,7 @@ services:
     environment:
       MINIO_ROOT_USER: ${MINIO_ROOT_USER:-minioadmin}
       MINIO_ROOT_PASSWORD: ${MINIO_ROOT_PASSWORD:-minioadmin}
+      MINIO_API_CORS_ALLOW_ORIGIN: ${S3_CORS_ALLOW_ORIGIN:-*}
     ports:
       - "${MINIO_API_PORT:-9000}:9000"
       - "${MINIO_CONSOLE_PORT:-9001}:9001"
@@ -91,9 +92,7 @@ services:
       - -ec
       - >
         mc alias set local http://minio:9000 ${MINIO_ROOT_USER:-minioadmin} ${MINIO_ROOT_PASSWORD:-minioadmin};
-        mc mb --ignore-existing local/${S3_BUCKET_NAME:-messenger-media};
-        printf '[{"AllowedHeaders":["*"],"AllowedMethods":["GET","PUT","POST","HEAD"],"AllowedOrigins":["%s"],"ExposeHeaders":["ETag"],"MaxAgeSeconds":3600}]' "${S3_CORS_ALLOW_ORIGIN:-*}" > /tmp/cors-rules.json;
-        mc cors set local/${S3_BUCKET_NAME:-messenger-media} /tmp/cors-rules.json
+        mc mb --ignore-existing local/${S3_BUCKET_NAME:-messenger-media}
     restart: "no"
 
   backend: