Update .env.sample and compose.yaml for Versity S3 Gateway to enhance WebUI and CORS configuration. Add comments clarifying the purpose of VGW_CORS_ALLOW_ORIGIN and correct usage of VGW_WEBUI_GATEWAYS, improving deployment instructions and user understanding.

komodo/s3/versitygw/compose.yaml

@@ -23,9 +23,11 @@ services:
       VGW_HEALTH: /_/health
       # WebUI (browser): separate listener; TLS terminates at Pangolin — serve HTTP in-container.
       VGW_WEBUI_NO_TLS: "true"
-      # Public base URL of the *S3 API* (same host you expose on port 10000 via Pangolin).
-      # Required for the WebUI JS to call the gateway (see Versity wiki / chart notes).
+      # Public base URL of the *S3 API* only (Pangolin → :10000). Not the WebUI hostname.
+      # No trailing slash. If this points at the UI URL, bucket ops return 404/wrong host.
       VGW_WEBUI_GATEWAYS: ${VGW_WEBUI_GATEWAYS}
+      # Browser Origin when WebUI and API use different HTTPS hostnames (see wiki / WebGUI CORS).
+      VGW_CORS_ALLOW_ORIGIN: ${VGW_CORS_ALLOW_ORIGIN}
     ports:
       - "${VERSITYGW_PORT:-10000}:10000"
       - "${VERSITYGW_WEBUI_PORT:-8080}:8080"