49 lines
2.1 KiB
YAML
49 lines
2.1 KiB
YAML
|
# minio_distributed defaults — 4-node distributed MinIO with EC:2
|
|||
|
|
# (single erasure set: 4 drives = 2 data + 2 parity, tolerates 2
|
|||
|
|
# simultaneous drive/node losses, 50% storage efficiency).
|
|||
|
|
#
|
|||
|
|
# Pinned to the same release as docker-compose so dev / prod parity
|
|||
|
|
# is preserved (a sneaky bucket-policy regression in a newer MinIO
|
|||
|
|
# release would otherwise show up first in prod).
|
|||
|
|
---
|
|||
|
|
minio_version: "RELEASE.2025-09-07T16-13-09Z"
|
|||
|
|
minio_arch: amd64
|
|||
|
|
|
|||
|
|
minio_port: 9000 # S3 API
|
|||
|
|
minio_console_port: 9001 # Web console
|
|||
|
|
minio_data_path: /var/lib/minio
|
|||
|
|
minio_etc: /etc/minio
|
|||
|
|
|
|||
|
|
# Erasure-coding parity. With 4 drives in the set the only viable
|
|||
|
|
# values are EC:2 (default) and EC:4 (mirror — wastes capacity).
|
|||
|
|
# EC:2 = 4 drives × 0.5 = 2 drives' worth of data, lose-2 OK.
|
|||
|
|
minio_storage_class_standard: "EC:2"
|
|||
|
|
|
|||
|
|
# Auth — placeholders. Override via Vault before applying to staging
|
|||
|
|
# or prod. The first task asserts these were overridden.
|
|||
|
|
minio_root_user: "CHANGE_ME_VAULT"
|
|||
|
|
minio_root_password: "CHANGE_ME_VAULT_PASSWORD"
|
|||
|
|
|
|||
|
|
# Bucket layout — `veza-prod-tracks` is the prod bucket holding
|
|||
|
|
# original audio files + HLS segments. Lifecycle policy lives in
|
|||
|
|
# templates/lifecycle.json.j2.
|
|||
|
|
minio_bucket_tracks: "veza-prod-tracks"
|
|||
|
|
|
|||
|
|
# Versioning retention for noncurrent versions of objects in the
|
|||
|
|
# tracks bucket. After this many days, expired noncurrent versions
|
|||
|
|
# are deleted. Keeps the bucket from growing unbounded under writers
|
|||
|
|
# that occasionally overwrite (album re-releases, re-encoded HLS).
|
|||
|
|
minio_noncurrent_version_expiry_days: 30
|
|||
|
|
|
|||
|
|
# Object age threshold for "cold" tier transition. v1.0 has no
|
|||
|
|
# remote tier configured (no Glacier / B2 backing yet) so this
|
|||
|
|
# directive is a placeholder — the lifecycle.json.j2 template emits
|
|||
|
|
# a *delete-marker expiration* rule by default and only emits a
|
|||
|
|
# transition rule if `minio_remote_tier_name` is non-empty.
|
|||
|
|
minio_cold_tier_after_days: 90
|
|||
|
|
minio_remote_tier_name: "" # e.g. "GLACIER" once a remote tier is wired
|
|||
|
|
|
|||
|
|
# `mc` (MinIO client) version used by the init task to create the
|
|||
|
|
# bucket + apply lifecycle. Pinned to the release matching the server.
|
|||
|
|
minio_mc_version: "RELEASE.2025-09-07T05-25-40Z"
|