forked from mtusi2026/mtusi2026lab4
MinIO community images can no longer be pulled on this arm64 host, so the stand runs RustFS 1.0.4 pinned by digest as non-root with a read only root, no published port, the console off and data on the s3data volume. A one-off s3-init with rc v0.1.36 creates the bucket, keeps it private for anonymous clients, creates the API user with a policy on the objects and listing of that one bucket, imports a lifecycle rule for incomplete multipart uploads and checks itself; the API replicas start only after it succeeded. Root keys reach only s3, s3-init and the operator s3-cli; the API gets its own key and the S3 settings through an anchor merged into its environment. secrets.sh creates hex S3 keys, the restart hook restarts S3 next to PostgreSQL and Valkey and waits until it is healthy, the limits policy covers the S3 services, and the stack evidence lists the new packages. The object storage adapter is tested against a throwaway RustFS of the same image: a 10 MiB round trip, a missing object, an idempotent delete and an unreachable endpoint failing within the request budget. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
13 lines
471 B
Bash
Executable File
13 lines
471 B
Bash
Executable File
#!/bin/sh
|
|
set -eu
|
|
cd "$(dirname "$0")/.."
|
|
defined=$(docker compose config --services)
|
|
stores=""
|
|
for service in ${STATE_SERVICES:-postgres valkey s3}; do
|
|
if printf '%s\n' "$defined" | grep -qx "$service"; then stores="$stores $service"; fi
|
|
done
|
|
[ -n "$stores" ] || { echo "no state services found" >&2; exit 3; }
|
|
docker compose stop lb "${API_SERVICE:-api}"
|
|
docker compose restart $stores
|
|
docker compose up -d --no-recreate --wait --wait-timeout "${WAIT_TIMEOUT:-75}"
|