Initialize second brain vault
This commit is contained in:
32
02_Projects/Home Lab Plan.md
Normal file
32
02_Projects/Home Lab Plan.md
Normal file
@@ -0,0 +1,32 @@
|
||||
# Home Lab Plan
|
||||
|
||||
## Phase 1 — establish control
|
||||
- Define production vs testing boundaries
|
||||
- Adopt a V1 remote-access model with Tailscale for admin and Cloudflare for user-facing app access
|
||||
- Define the backup strategy and restore expectations
|
||||
- Inventory the current workloads more precisely
|
||||
- Avoid adding many new services until the platform is clearer
|
||||
|
||||
## Phase 2 — stabilize core services
|
||||
- Confirm where drive/files should live short-term
|
||||
- Confirm where photo management should live short-term
|
||||
- Decide whether Synology remains the production home for some services during transition
|
||||
- Introduce identity/access management only once the service map is clear
|
||||
|
||||
## Phase 3 — controlled evolution
|
||||
- Evaluate Nextcloud migration path
|
||||
- Evaluate Immich migration path
|
||||
- Evaluate Authentik or equivalent
|
||||
- Review whether Proxmox should be the central app platform
|
||||
- Revisit edge/remote-access complexity and reduce overlap where possible
|
||||
|
||||
## What Orik should track
|
||||
- infra changes
|
||||
- service locations
|
||||
- architecture decisions
|
||||
- backup changes
|
||||
- migration plans
|
||||
- risks / TODOs
|
||||
|
||||
## Current concern
|
||||
The likely failure mode is not lack of capability; it is too many overlapping tools and unclear boundaries.
|
||||
Reference in New Issue
Block a user