Add Phase 5: explanation documentation #96
3 changed files with 6 additions and 0 deletions
Add AI authorship disclaimer to explanation articles
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
commit
c052d11422
|
|
@ -7,6 +7,8 @@ tags:
|
|||
|
||||
# Architecture Overview
|
||||
|
||||
> **Note:** This article was drafted by AI and reviewed by Erich. I plan to rewrite all explanatory content in my own words - these serve as placeholders to establish the documentation structure.
|
||||
|
||||
How all the BlumeOps pieces fit together.
|
||||
|
||||
## Physical Layer
|
||||
|
|
|
|||
|
|
@ -7,6 +7,8 @@ tags:
|
|||
|
||||
# Security Model
|
||||
|
||||
> **Note:** This article was drafted by AI and reviewed by Erich. I plan to rewrite all explanatory content in my own words - these serve as placeholders to establish the documentation structure.
|
||||
|
||||
How BlumeOps handles network security, secrets, and access control.
|
||||
|
||||
## Network Security: Tailscale
|
||||
|
|
|
|||
|
|
@ -7,6 +7,8 @@ tags:
|
|||
|
||||
# Why GitOps?
|
||||
|
||||
> **Note:** This article was drafted by AI and reviewed by Erich. I plan to rewrite all explanatory content in my own words - these serve as placeholders to establish the documentation structure.
|
||||
|
||||
BlumeOps uses GitOps principles for managing personal infrastructure. This might seem like overkill for a homelab, but there are good reasons.
|
||||
|
||||
## The Problem with Manual Infrastructure
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue