Repository navigation
feat: add VersityGW template - #1171
Conversation
S3-compatible gateway over a POSIX backend with versioning, flat-file IAM and the built-in WebUI exposed on the domain; S3 API and admin API ports stay internal per the upstream Docker guide.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
|
Pushed a small follow-up to this branch \u2014 head is now |
|
Hi! This PR is blocked waiting for review/approval. Could you please review when you have a chance? The changes are ready and all local checks pass. Thanks! |
|
Friendly ping — this adds a VersityGW template. Ready for review; happy to adjust anything. Thanks! |
|
Approved, thanks! |
|
Thanks! Quick state summary in case anything is needed from my side before merge:
One thing to confirm during review: |
|
@Siumauricio thanks! One mechanical thing: "Approved, thanks!" landed as an issue comment, and Could you re-submit it as a formal review (Review changes → Approve)? Nothing else is missing:
Happy to answer the icon question too — if the template needs a specific logo asset, say which format and I'll add it in the same branch. |
/claim #1161
Adds the VersityGW template requested in #1161 — a high-performance S3-compatible gateway (MinIO alternative) with:
/data/s3, object versioning at/data/versioning, flat-file IAM at/data/iam(named volumes, per the upstream Docker guide)VGW_WEBUI_NO_TLS=truesince Dokploy terminates TLS at the proxy7070) and Admin API (7071) kept internal — the WebUI reaches them over the container networkROOT_ACCESS_KEY/ROOT_SECRET_KEYcredentialsStructure mirrors the merged SFTPGo/SFTPGo-style blueprints:
docker-compose.yml,template.toml,meta.json, logo.Tested values against upstream docs:
versity/versitygw:v1.8.0(latest tag on Docker Hub)VGW_BACKEND,VGW_PORT,VGW_ADMIN_PORT,VGW_WEBUI_PORT,VGW_IAM_DIR,VGW_VERSIONING_DIR,VGW_WEBUI_*) from the official Docker wiki