ginnoir
7c7f6dfebc
Protects /config, selective labdata, and nightly DB dumps; documents homelab improvement plan briefs.
1.2 KiB
1.2 KiB
TB-010 — dev stack.env migration
Status: not started
Your call: (unset — talk first)
Talk first
Stop. Don't read Reference until we've talked. In chat, say "let's do TB-010" or "dev stack.env migration".
In one sentence: Make the dev stack use stack.env like everything else — no Portainer UI env vars.
Why it came up: Every other stack commits secrets to stack.env; dev still needs UI mirroring (footgun).
Questions
- Have you been bitten by dev env drift before?
- Worth an afternoon, or low priority housekeeping?
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
stacks/dev/
If we do it — rough steps
- Move all ${VAR} into stack.env
- Deploy, verify Gitea/Plane/BookStack/code-server
- Clear Portainer UI env vars
Done when
- Dev stack runs with env_file only