coilysiren/website
1
0
Fork 0
Code Issues 14 Pull requests Projects Releases Packages Wiki Activity Actions 3

Blog post: Why my homelab doesn't use Terraform #14

New issue
Closed
opened 2026-05-23 20:55:40 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:55:40 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-03T19:53:33Z - https://github.com/coilysiren/website/issues/1346

🤖 Filed by Claude Code on Kai's behalf.

Working title: Why my homelab doesn't use Terraform (and what it uses instead)

Hook: Bio says Terraform. The homelab doesn't run on it. Here's why, and what shape IaC actually takes when the substrate is one person, one box, and k3s.

Beats:

  • The default "real engineers use Terraform for everything" narrative.
  • What the homelab actually uses (Pulumi for AWS, invoke tasks for k3s, raw manifests, systemd units committed to infrastructure/).
  • The cost/benefit math: state files, drift detection, and provider sprawl vs. one operator.
  • When TF would start to earn its keep here (multi-region, multi-environment, team).
  • Honest closer: the bio claim is from work, not the homelab; here is the public evidence of the work-side TF use ([link to OSS contribution if/when one lands]).

Why now: turns the portfolio gap into a position piece instead of a credibility tax.

Audience: platform engineers and IaC opinion-havers. Likely to provoke; that is fine.

🤖 Filed by Claude Code on Kai's behalf.

Moved from coilysiren/coilyco-ai#10.

_Originally filed by @coilysiren on 2026-05-03T19:53:33Z - [https://github.com/coilysiren/website/issues/1346](https://github.com/coilysiren/website/issues/1346)_ > 🤖 Filed by Claude Code on Kai's behalf. **Working title:** Why my homelab doesn't use Terraform (and what it uses instead) **Hook:** Bio says Terraform. The homelab doesn't run on it. Here's why, and what shape IaC actually takes when the substrate is one person, one box, and k3s. **Beats:** - The default "real engineers use Terraform for everything" narrative. - What the homelab actually uses (Pulumi for AWS, invoke tasks for k3s, raw manifests, systemd units committed to `infrastructure/`). - The cost/benefit math: state files, drift detection, and provider sprawl vs. one operator. - When TF would start to earn its keep here (multi-region, multi-environment, team). - Honest closer: the bio claim is from work, not the homelab; here is the public evidence of the work-side TF use ([link to OSS contribution if/when one lands]). **Why now:** turns the portfolio gap into a position piece instead of a credibility tax. **Audience:** platform engineers and IaC opinion-havers. Likely to provoke; that is fine. > 🤖 Filed by Claude Code on Kai's behalf. --- *Moved from coilysiren/coilyco-ai#10.*
coilysiren commented 2026-05-30 05:43:04 +00:00
Author
Owner
Copy link

Iceboxed in the 2026-05-29 backlog burn-down: Speculative blog post draft. Reopen anytime if it becomes real.

Iceboxed in the 2026-05-29 backlog burn-down: Speculative blog post draft. Reopen anytime if it becomes real.
coilysiren 2026-05-30 05:43:04 +00:00
  • closed this issue
  • added the
    icebox
         label
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
og-article-tags-1373
claude/coily-docker-image-FF2Rw
No results found.
Labels
Clear labels   
icebox
Closed in the 2026-05-29 backlog burn-down; reopen if it becomes real

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
P4

No labels
icebox
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilysiren/website#14
No description provided.