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.
|
||||
36
02_Projects/Home Lab.md
Normal file
36
02_Projects/Home Lab.md
Normal file
@@ -0,0 +1,36 @@
|
||||
# Home Lab
|
||||
|
||||
## Status
|
||||
Active
|
||||
|
||||
## Goal
|
||||
Design and evolve a simple, well-documented, production-grade homelab with clear separation between production and testing, strong backups, and architecture that Claudio can trust for family and friends.
|
||||
|
||||
## Priorities
|
||||
- Keep the system understandable
|
||||
- Avoid starting with too many apps
|
||||
- Build strong backup and recovery foundations
|
||||
- Separate production from testing
|
||||
- Document architecture and changes clearly
|
||||
|
||||
## Current target apps
|
||||
- File sync / drive
|
||||
- Photo management
|
||||
- Media hosting
|
||||
- Identity / access management
|
||||
|
||||
## Current app direction
|
||||
- Today: Synology Drive, Synology Photos, Jellyfin, Plex
|
||||
- Likely future: Nextcloud, Immich, Authentik
|
||||
|
||||
## Key requirements
|
||||
- production vs testing separation
|
||||
- solid backup strategy
|
||||
- remote access strategy
|
||||
- architecture clarity
|
||||
- ability to evolve gradually
|
||||
|
||||
## Related
|
||||
- [[05_Resources/Home Lab Inventory]]
|
||||
- [[05_Resources/Home Lab Architecture]]
|
||||
- [[06_Decisions/Home Lab Principles]]
|
||||
22
02_Projects/Job Hunt.md
Normal file
22
02_Projects/Job Hunt.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# Job Hunt
|
||||
|
||||
## Status
|
||||
Active
|
||||
|
||||
## Role of Orik
|
||||
Track progress, opportunities, decisions, materials, and next steps.
|
||||
|
||||
## Goal
|
||||
Help Claudio run a focused, well-documented job search without losing context across conversations.
|
||||
|
||||
## What should be tracked here
|
||||
- target roles and themes
|
||||
- companies of interest
|
||||
- applications sent
|
||||
- interview stages
|
||||
- materials to improve
|
||||
- strategic decisions
|
||||
- blockers and next actions
|
||||
|
||||
## Notes
|
||||
This project was already active in Telegram and should be treated as one of Claudio's main current projects.
|
||||
Reference in New Issue
Block a user