Files
home-server/komodo/s3/versitygw/compose.yaml

52 lines
1.5 KiB
YAML

# Versity S3 Gateway — POSIX backend over Docker volumes.
# https://github.com/versity/versitygw
services:
versitygw:
image: versity/versitygw:v1.3.1
container_name: versitygw
restart: unless-stopped
# Credentials: use `${VAR}` so values come from the same env Komodo passes with
# `docker compose --env-file <run_directory>/.env` (see Komodo Stack docs).
# Do NOT use `env_file: .env` here: that path is resolved next to *this* compose
# file, while Komodo writes `.env` under `run_directory` — they often differ
# (e.g. run_directory = repo root, compose in komodo/s3/versitygw/).
environment:
ROOT_ACCESS_KEY: ${ROOT_ACCESS_KEY}
ROOT_SECRET_KEY: ${ROOT_SECRET_KEY}
ROOT_ACCESS_KEY_ID: ${ROOT_ACCESS_KEY_ID}
ROOT_SECRET_ACCESS_KEY: ${ROOT_SECRET_ACCESS_KEY}
# Matches Helm chart default; enables `/_/health` for probes.
VGW_HEALTH: /_/health
ports:
- "${VERSITYGW_PORT:-10000}:10000"
volumes:
- /mnt/nfs/versity/s3:/data/s3
- /mnt/nfs/versity/iam:/data/iam
- /mnt/nfs/versity/versions:/data/versions
command:
- "--port"
- ":10000"
- "--iam-dir"
- "/data/iam"
- "posix"
- "--versioning-dir"
- "/data/versions"
- "/data/s3"
healthcheck:
test:
[
"CMD",
"wget",
"-qO-",
"http://127.0.0.1:10000/_/health",
]
interval: 30s
timeout: 5s
retries: 3
start_period: 10s
volumes:
s3_data:
iam:
versions: