Operate Joel's Garage S3-compatible object storage on three-body. Use for Garage, Convex Garage, Garage S3, three-body Garage, port 39100, Garage buckets, and MinIO-to-Garage migration.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Operate Joel's canonical S3-compatible object storage for local self-hosted Convex. This is not generic Garage advice. The canonical path is the Docker/Compose Garage service running on the ASUSTOR NAS three-body.
Custom MinIO is now a rollback/reference path. ASUSTOR MinIO CE is only a smoke-test/reference instance.
Use this skill when Joel mentions:
three-body Garage39100If the task is about the full local Convex runtime, also read the local-convex skill. If the task is about general ASUSTOR storage, NFS, SMB, RAID, or NAS health, also read the three-body skill. If the task is explicitly about MinIO rollback or CE cleanup, also read the minio skill.
Host:
three-body100.67.156.415.1.3.RI81Canonical Garage:
http://100.67.156.41:39100/volume1/joelclaw/s3/garage/data/volume1/joelclaw/s3/garage/meta/volume1/joelclaw/s3/garage/snapshots/volume1/joelclaw/s3/garage-compose/compose.yaml/volume1/joelclaw/s3/garage-compose/garage.toml/volume1/joelclaw/s3/garage-compose/convex-s3.env/volume1/joelclaw/s3/garage-compose/convex-s3.redacted.env/volume1/joelclaw/s3/install-three-body-convex-garage.sh/Users/joel/Documents/Codex/2026-06-17/we-re-setting-up-durable-self/outputs/install-three-body-convex-garage.shdxflrs/garage@sha256:dac0c92add4f1a0b41035e94b41036a270ffbe88a37c7ac9c3f19e6dc5bdccf2Do not expose Garage publicly. Keep S3 API access LAN/tailnet only.
Read these before mutating the setup:
/Users/joel/.brain/projects/convex-self-hosting-local.svx/Users/joel/Documents/Codex/2026-06-17/we-re-setting-up-durable-self/outputs/install-three-body-convex-garage.sh/volume1/joelclaw/s3/garage-compose/compose.yaml/volume1/joelclaw/s3/garage-compose/convex-s3.redacted.envIf sources disagree, prefer the brain project note, then verify live state with redaction-safe health checks. Do not print raw env files to resolve disagreement.
Never print, paste, summarize, commit, or log:
convex-s3.env.envIt is okay to read and report the redacted env file. It is okay to say whether required keys exist. It is not okay to reveal their values.
Before sharing command output, scan it for:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYGARAGE_RPC_SECRETGARAGE_ADMIN_TOKENGARAGE_METRICS_TOKENCONVEX_ACCESS_KEY_IDCONVEX_SECRET_ACCESS_KEYconvex-s3.envRedact first, then report.
Use one SSH session to three-body at a time. NAS SSH is sensitive to bursts and can reset handshakes after rapid parallel probes.
Default read-only SSH shape:
ssh -o BatchMode=yes -o ConnectTimeout=8 joel@three-body 'uptime; pwd'Operational rules:
kex_exchange_identification, Not allowed at this time, or repeated SSH resets.sudo or an ADM/admin path.Prefer network checks that do not require credentials:
nc -vz -w 5 100.67.156.41 39100
curl -sS -m 5 -o /tmp/garage-root.out -w '%{http_code}\n' http://100.67.156.41:39100/
sed -n '1,3p' /tmp/garage-root.outGarage does not support anonymous S3 access; 403 AccessDenied from / proves the API is reachable.
Redaction-safe env check:
ssh joel@three-body 'awk -F= "/^(AWS_REGION|S3_ENDPOINT_URL|AWS_S3_FORCE_PATH_STYLE|S3_STORAGE_)/ {print}" /volume1/joelclaw/s3/garage-compose/convex-s3.env'Presence-only secret check:
ssh joel@three-body 'awk -F= "/^(AWS_ACCESS_KEY_ID|AWS_SECRET_ACCESS_KEY)=/ {print $1\"=<present>\"}" /volume1/joelclaw/s3/garage-compose/convex-s3.env'Service checks usually need sudo:
ssh joel@three-body 'sudo docker ps --format "table {{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}" | grep -Ei "garage|39100" || true'
ssh joel@three-body 'cd /volume1/joelclaw/s3/garage-compose && sudo docker compose ps'Do not run logs without a reason. If logs are needed, bound them and redact:
ssh joel@three-body 'cd /volume1/joelclaw/s3/garage-compose && sudo docker compose logs --tail=120 garage'Garage should have these Convex buckets:
joelclaw-local-usw2-convex-exportsjoelclaw-local-usw2-convex-snapshot-importsjoelclaw-local-usw2-convex-modulesjoelclaw-local-usw2-convex-filesjoelclaw-local-usw2-convex-searchBucket rules:
http://100.67.156.41:39100.Convex should point at the Garage IP endpoint:
AWS_REGION=usw2
S3_ENDPOINT_URL=http://100.67.156.41:39100
AWS_S3_FORCE_PATH_STYLE=true
AWS_ACCESS_KEY_ID=<from /volume1/joelclaw/s3/garage-compose/convex-s3.env>
AWS_SECRET_ACCESS_KEY=<from /volume1/joelclaw/s3/garage-compose/convex-s3.env>
S3_STORAGE_EXPORTS_BUCKET=joelclaw-local-usw2-convex-exports
S3_STORAGE_SNAPSHOT_IMPORTS_BUCKET=joelclaw-local-usw2-convex-snapshot-imports
S3_STORAGE_MODULES_BUCKET=joelclaw-local-usw2-convex-modules
S3_STORAGE_FILES_BUCKET=joelclaw-local-usw2-convex-files
S3_STORAGE_SEARCH_BUCKET=joelclaw-local-usw2-convex-searchValidation rules:
S3_ENDPOINT_URL must be http://100.67.156.41:39100.AWS_S3_FORCE_PATH_STYLE must be true.When wiring or debugging Garage for local Convex:
39100.S3_ENDPOINT_URL=http://100.67.156.41:39100.cd /Users/joel/Documents/Codex/2026-06-17/we-re-setting-up-durable-self/work/local-convex
./smoke-self-hosted-convex.shcustom-garage and http://100.67.156.41:39100.403 AccessDenied from / is expected.39100; custom MinIO is 39000; CE is 29990.sudo.joelhooks/joelclaw
1fb2468
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.