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/.env.sample

@@ -21,10 +21,16 @@ VERSITYGW_PORT=10000
 # WebUI (container listens on 8080). In Pangolin, create a *second* HTTP resource for this
 # port — do not point the UI hostname at :10000 (that is S3 API only; `/` is not the SPA).
 VERSITYGW_WEBUI_PORT=8080
-# HTTPS URL clients use for the S3 API (must match your Pangolin route to :10000), e.g.:
+# HTTPS URL of the *S3 API* (Pangolin resource → host :10000). **Not** the WebUI URL.
+# No trailing slash. Wrong value → WebUI calls the wrong host and bucket create can 404.
 # VGW_WEBUI_GATEWAYS=https://s3.example.com
 VGW_WEBUI_GATEWAYS=
 
+# Public origin of the **WebUI** page (Pangolin → :8080), e.g. https://s3-ui.example.com
+# Required when UI and API are on different hosts so the browser can call the API (CORS).
+# VGW_CORS_ALLOW_ORIGIN=https://s3-ui.example.com
+VGW_CORS_ALLOW_ORIGIN=
+
 # NFS: object metadata defaults to xattrs; most NFS mounts need sidecar mode
 # (compose.yaml uses --sidecar /data/sidecar). Create the host path, e.g.
 #   mkdir -p /mnt/nfs/versity/sidecar