# TB-017 — One MinIO instead of three

**Status:** dropped
**Your call:** _(unset — talk first)_

---

## Talk first

> **Stop.** Don't read Reference until we've talked.
> In chat, say **"let's do TB-017"** or **"one minio instead of three"**.

**In one sentence:** resume, famapp, and Plane each run their own MinIO — could be one server, three buckets.

**Why it came up:** Less ops; slightly higher blast radius if MinIO dies.

### Questions

1. Do the three MinIO instances cause you pain today?
2. If no — drop; isolation is fine.

### Your options

| Option | Meaning |
|--------|---------|
| **Do it** | We're doing this — I'll implement or walk you through it |
| **Later** | Keep on the list, not now |
| **Drop** | Remove from plan — totally fine |
| **Tweak** | Change scope; tell me how |

### What we decided

| | |
|---|---|
| **Decision** | |
| **Notes** | |
| **Date** | |

---

<details>
<summary>Reference (only open if we're doing it)</summary>

### Stack / files

resume, famapp, dev

### If we do it — rough steps

1. Decision
2. If yes: migrate buckets, update env vars

### Done when

- [ ] Consolidated or explicitly kept separate

</details>