Files
ginnoirandClaude Sonnet 4.6 11f51559b0 chore(plans): record new service decisions and drop list
New services: all in except TB-020 Mealie (deferred to famapp).
Active interest: TB-015 Vault, TB-027 Jellyfin, TB-028 HA, TB-031 Pingvin.
Dropped: TB-017 MinIO consolidation, TB-018 Plane, TB-029 Firefly III,
TB-030 AdGuard (handled at router), TB-032 Wiki.js (using BookStack).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-15 22:08:55 -05:00

1.2 KiB

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

Reference (only open if we're doing it)

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