Update Project Scope v2.1 - Corrected game servers, added Code-Server, current state

This commit is contained in:
Firefrost Automation
2026-02-11 19:27:07 -06:00
parent 5ea97828a7
commit afd54be50c

View File

@@ -1,13 +1,14 @@
# 🔥❄️ FIREFROST GAMING: PROJECT SCOPE V2.0
# 🔥❄️ FIREFROST GAMING: PROJECT SCOPE V2.1
**The Complete Technical & Business Vision**
---
**Document Version:** 2.0
**Created:** February 9, 2026
**Supersedes:** firefrost-master-implementation-plan.md (v1.0)
**Status:** ✅ CURRENT - Single Source of Truth
**Document Version:** 2.1
**Created:** February 9, 2026
**Last Updated:** February 11, 2026
**Supersedes:** FIREFROST-PROJECT-SCOPE-V2.0 (Feb 9, 2026)
**Status:** ✅ CURRENT - Single Source of Truth
**Next Review:** March 1, 2026
---
@@ -16,11 +17,12 @@
Firefrost Gaming is a subscription-based Minecraft server network built on the philosophy of balance: **Fire + Frost = Where Passion Meets Precision.**
**Current Status (Feb 9, 2026):**
**Current Status (Feb 11, 2026):**
- 12 game servers operational (6 NC1, 6 TX1)
- Phase 0.5 at 100% (5/5 management services deployed)
- 5 management services deployed (Gitea, Uptime Kuma, MkDocs, Code-Server, Automation)
- 17 Uptime Kuma monitors active (5 infrastructure + 12 game servers)
- Automation system operational (95% reduction in manual work)
- Three-tier documentation architecture planned
- Three-tier documentation architecture in progress
**Leadership:**
- **Michael "Frostystyle" Krause** - Technical Lead (The Wizard)
@@ -50,72 +52,115 @@ Firefrost Gaming is a subscription-based Minecraft server network built on the p
## 🏗️ INFRASTRUCTURE STATUS
### Deployed Services (Phase 0.5: 100% Complete)
### Server Inventory (6 Servers)
**✅ Service 1/5: Gitea** (git.firefrostgaming.com)
| Server | Role | IP Address | Specs | Location |
| :---- | :---- | :---- | :---- | :---- |
| **TX1 Dallas** | Game Servers ONLY | 38.68.14.26 | 32 vCPU, 256GB RAM, 1TB | Dallas, TX |
| **NC1 Charlotte** | Game Servers ONLY | 216.239.104.130 | 32 vCPU, 256GB RAM, 100GB | Charlotte, NC |
| **Panel** | Pterodactyl Control Plane | 45.94.168.138 | VPS | - |
| **Command Center** | Management Hub | 63.143.34.217 | VPS | Dallas, TX |
| **Billing** | Paymenter Portal | 38.68.14.188 | VPS | - |
| **Ghost** | Documentation Cluster | 64.50.188.14 | VPS | - |
**Architecture:** "Backend on Command Center, Frontend on Ghost, Money on Billing, Games on Dedis, Control on Panel"
### Deployed Management Services
**✅ Service 1: Gitea** (git.firefrostgaming.com)
- Git version control for all infrastructure
- Location: Command Center VPS
- Deployed: Feb 8-9, 2026
- SSL enabled, GitHub mirror configured
- SSL enabled, GitHub mirror configured (auto-sync)
- All configs version-controlled
**✅ Service 2/5: Uptime Kuma** (uptime.firefrostgaming.com)
- Infrastructure monitoring
**✅ Service 2: Uptime Kuma** (status.firefrostgaming.com)
- Infrastructure + game server monitoring
- Location: Command Center VPS
- Deployed: Feb 9, 2026
- Discord integration active
- 6 monitors operational
- Discord integration active (#network-status)
- 17 monitors: 5 infrastructure + 12 game servers
- NC1 routing resolved (reachable from Command Center)
**✅ Service 3/5: MkDocs** (docs.firefrostgaming.com)
- PUBLIC documentation (Git-native)
**✅ Service 3: MkDocs** (docs.firefrostgaming.com)
- PUBLIC documentation portal (Git-native)
- Location: Ghost VPS
- Deployed: Feb 9, 2026
- Material theme, search enabled
- Markdown in Gitea → Auto-builds HTML
**✅ Service 4/5: Wiki.js Subscribers** (subscribers.firefrostgaming.com)
- SUBSCRIBER documentation portal
- Planned deployment: Feb 9 (afternoon)
- Role-based access control
- Git-first workflow
**✅ Service 4: Automation System**
- Automated deployment and operations framework
- Location: Command Center VPS
- Deployed: Feb 9, 2026
- 95% reduction in manual operations
- Medical necessity for hand limitations
**✅ Service 5/5: Wiki.js Staff
✅ Service 6/7: MkDocs
✅ Service 7/7: NextCloud** (downloads.firefrostgaming.com)
- World downloads for subscribers
- File hosting optimized
- Planned deployment: Feb 9 (afternoon)
**✅ Service 5: Code-Server** (code.firefrostgaming.com)
- Browser-based VS Code IDE
- Location: Command Center VPS
- Deployed: Feb 11, 2026
- File editing + built-in terminal
- Eliminates SSH copy-paste for documentation work
### Pending Management Services
**⏳ Service 6: NextCloud** (downloads.firefrostgaming.com)
- World downloads, video archive, file hosting
- Location: Ghost VPS
- Priority: HIGH (three use cases identified)
**⏳ Service 7: Wiki.js Subscribers** (subscribers.firefrostgaming.com)
- SUBSCRIBER documentation portal
- Location: Ghost VPS
- Role-based access control
**⏳ Service 8: Wiki.js Staff** (staff.firefrostgaming.com)
- STAFF-only internal documentation
- Location: Ghost VPS
- Admin/staff access only
**⏳ Service 9: Vaultwarden** (vault.firefrostgaming.com)
- Password management
- Priority: LOW
**⏳ Service 10: Netdata** (analytics.firefrostgaming.com)
- Server analytics and performance monitoring
- Priority: LOW
### Game Servers (12 Total)
**NC1 Charlotte (6 servers):**
- The Ember Project (216.239.104.130:25565)
- Minecolonies (216.239.104.131:25565)
- All The Mods 10 (216.239.104.134:25565)
- Homestead (216.239.104.133:25566)
- Hytale (216.239.104.131:5520)
- EMC Subterra Tech (216.239.104.132:25566)
**TX1 Dallas (6 servers) — Each on own IP:**
**TX1 Dallas (6 servers):**
- Stoneblock 4 (38.68.14.26:25565)
- Reclamation (38.68.14.27:25565)
- Society: Sunlit Valley (38.68.14.28:25565)
- Vanilla 1.21.1 (38.68.14.29:25565)
- All The Mons (38.68.14.30:25565)
- FoundryVTT (38.68.14.26:30000)
| Server | IP | Port | Notes |
| :---- | :---- | :---- | :---- |
| Stoneblock 4 | 38.68.14.26 | 25565 | |
| Reclamation | 38.68.14.27 | 25565 | |
| Society: Sunlit Valley | 38.68.14.28 | 25565 | |
| Vanilla 1.21.11 | 38.68.14.29 | 25565 | |
| All The Mons | 38.68.14.30 | 25565 | |
| FoundryVTT | 38.68.14.26 | 30000 | Holly's Pokerole campaign |
### Hardware
**NC1 Charlotte (6 servers) — All on single IP, unique ports:**
**TX1 Dallas:** 32 vCPU, 256GB RAM (99% idle - management services hub)
**NC1 Charlotte:** 32 vCPU, 256GB RAM (game servers)
**Command Center:** Reserved for future DDoS protection (GRE tunnels)
| Server | IP | Port | Notes |
| :---- | :---- | :---- | :---- |
| The Ember Project | 216.239.104.130 | 25565 | |
| Minecolonies: Create and Conquer | 216.239.104.130 | 25566 | |
| All The Mods 10 | 216.239.104.130 | 25569 | 20GB RAM (memory leak, monitor) |
| EMC Subterra Tech | 216.239.104.130 | 25571 | |
| Homestead | 216.239.104.130 | 25572 | |
| Hytale | 216.239.104.130 | 5520 | |
---
## 🤖 AUTOMATION SYSTEM (NEW!)
## 🤖 AUTOMATION SYSTEM
### The Firefrost Automation Framework
**Deployed:** February 9, 2026
**Impact:** 95% reduction in manual operations
**Location:** `/root/firefrost-work/firefrost-operations-manual/automation/`
**Deployed:** February 9, 2026
**Impact:** 95% reduction in manual operations
**Location:** Command Center — `/root/firefrost-work/firefrost-operations-manual/automation/`
**How It Works:**
```
@@ -127,24 +172,7 @@ Git → Results committed back automatically
Claude → Reads results from GitHub mirror
```
**Key Components:**
- `automation-daemon.sh` - Background watcher (PID management)
- `executor.sh` - Task runner with auto-commit
- `queue/` - Tasks waiting to execute
- `results/` - Execution output (committed to Git)
- `logs/` - Completed tasks archive
**Success Metrics:**
- Test Task 001: SUCCESS (exit 0)
- Test Task 002: SUCCESS (automated execution)
- BookStack deployment: 2 minutes (previously would take 20+ minutes)
- MkDocs deployment: 1.5 minutes
**Accessibility Impact:**
- Michael's hand limitations accommodated
- Single paste operation per deployment
- All work auditable in Git history
- Perfect for marathon sessions
**Why It Exists:** Medical necessity. Michael's permanent hand nerve damage means every paste operation requires physical effort. This system reduces 10-20 pastes to ONE paste per task.
---
@@ -157,32 +185,19 @@ Claude → Reads results from GitHub mirror
- Authentication: None required
- Content: Server rules, getting started, modpack info
- Workflow: Edit markdown in Gitea → Auto-rebuild
- Status: ✅ DEPLOYED Feb 9, 2026
- Status: ✅ DEPLOYED
**Tier 2: SUBSCRIBERS (subscribers.firefrostgaming.com + downloads.firefrostgaming.com)**
- Documentation: Wiki.js (premium guides, exclusive content)
- Downloads: NextCloud (world backups, custom modpacks)
- Downloads: NextCloud (world backups, custom modpacks, video archive)
- Authentication: Subscriber login required
- Content: Premium guides, world downloads, exclusive perks
- Workflow: Edit in Wiki.js UI OR Git
- Status: ⏳ DEPLOYING Feb 9 afternoon
- Status: ⏳ PENDING
**Tier 3: STAFF (staff.firefrostgaming.com)**
- Technology: Wiki.js
- Authentication: Staff/Admin only
- Content: SOPs, admin procedures, internal guides
- Workflow: Edit in Wiki.js UI OR Git
- Status: ⏳ DEPLOYING Feb 9 afternoon
### Why Three Tiers?
**Problem Solved:**
- Public can access basic info (no barriers)
- Subscribers get premium value (world downloads!)
- Staff have secure internal documentation
- Each tier isolated (different security boundaries)
- Git-first workflow maintained (Michael's requirement)
- UI-first editing available (Meg's preference)
- Status: ⏳ PENDING
---
@@ -205,7 +220,7 @@ Claude → Reads results from GitHub mirror
**$5/month - "Elemental Tier"**
- CHOOSE YOUR PATH: Fire or Frost
- Full server access (13+ modpacks)
- Full server access (12+ modpacks)
- Subscriber documentation portal
- World download access (30-day retention)
- Priority support
@@ -239,8 +254,6 @@ Claude → Reads results from GitHub mirror
- Focus: Collaborative builds, exploration, creativity
- Led by: Frostystyle (The Wizard)
**Competitive Element:** Michael vs Meg - who recruits more to their path?
---
## 🔐 AUTHENTICATION STRATEGY
@@ -248,27 +261,43 @@ Claude → Reads results from GitHub mirror
### Phased Implementation
**Phase 1: Manual Management** (Current - Launch to 20 subscribers)
- Subscriber pays via Paymenter
- Manual account creation (Wiki.js + NextCloud)
- Email credentials
- Manual account creation
- Track expirations in spreadsheet
- **Advantage:** Zero dev time, validates market
- Zero dev time, validates market
**Phase 2: Webhook Automation** (20+ subscribers)
- Paymenter webhooks trigger scripts
- Automatic account creation/deletion
- Automated credential emails
- **Development:** 3-4 hours
- **Trigger:** When manual work becomes burden
- Development: 3-4 hours
**Phase 3: SSO/OAuth** (100+ subscribers - optional)
- Single sign-on across all services
- Real-time subscription validation
- Enterprise-grade auth
- **Development:** 8-12 hours
- **Trigger:** Only if subscriber count justifies complexity
- Development: 8-12 hours
- Only if subscriber count justifies complexity
**Decision:** Start Phase 1, upgrade to Phase 2 when needed
---
## 🛡️ PHASE 1: DDoS PROTECTION SYSTEM
### Overview
**Status:** Planning Phase
**Priority:** Deploy after management services complete, before soft launch
**Purpose:** Replace dismantled Phase 0 GRE system with reliable protection
### Options Under Consideration
**Option A: Cloudflare Spectrum** — Managed service, low maintenance
**Option B: Simplified GRE + Cloudflare** — More control, careful implementation
**Option C: Hybrid** — VPS behind Cloudflare, game servers with lightweight protection
**Decision Point:** Design session after Phase 0.5+ completion
### Success Metrics
- Withstands common DDoS attacks (volumetric, SYN floods)
- 99.9%+ uptime during normal operations
- < 1 hour maintenance per month
- Zero "midnight emergency" pages
---
@@ -292,164 +321,56 @@ Claude → Reads results from GitHub mirror
- Text: #FFFFFF / #000000
### Logos & Assets
**Location:** `/root/firefrost-master-configs/branding/`
- Circular Emblem (512x512) - Social profiles, favicon
- Light Logo - Light backgrounds
- Dark Logo - Dark backgrounds, website
- Backgrounds - Hero images, Discord, social media
- Character Sprites - Gingerfury (Fire) + Frostystyle (Frost)
---
---
## 🛡️ PHASE 1: DDoS PROTECTION SYSTEM
### Overview
**Status:** Planning Phase
**Priority:** Deploy after Phase 0.5 completion, before soft launch
**Purpose:** Replace dismantled Phase 0 GRE system with reliable protection
### Phase 0 Context (Completed)
**What Was Dismantled:**
- Complex GRE tunnel configuration
- IP cloaking system prone to failures
- Over-engineered solution causing more problems than it solved
**Why It Was Removed:**
- Frequent connectivity issues
- Difficult to troubleshoot
- Required constant maintenance
- Prevented reliable infrastructure operations
### Phase 1 Goals
**Primary Objective:** Implement "good enough" DDoS protection that:
- ✅ Protects against common attacks (Layer 3/4)
- ✅ Doesn't break during normal operations
- ✅ Easy to maintain and troubleshoot
- ✅ Minimal complexity vs Phase 0
**NOT trying to:**
- ❌ Defend against state-level actors
- ❌ Create perfect invisibility
- ❌ Over-engineer like Phase 0
### Proposed Architecture (To Be Designed)
**Option A: Cloudflare Spectrum (Simplest)**
- Pros: Managed service, no infrastructure complexity
- Cons: Monthly cost, less control
- Best for: Quick deployment, low maintenance
**Option B: Simplified GRE + Cloudflare**
- Pros: More control, proven technology
- Cons: Requires careful implementation
- Best for: Custom requirements, cost control
**Option C: Hybrid Approach**
- VPS services behind Cloudflare
- Game servers with lightweight protection
- Best for: Tiered protection based on risk
**Decision Point:** Design session after Phase 0.5 completion
### Implementation Timeline
**Pre-Launch Requirements:**
1. Assess actual threat level (public launch = attack surface)
2. Design session: Choose architecture
3. Document decision rationale
4. Test implementation on non-critical service
5. Deploy to production
**Estimated Effort:** 4-8 hours (depends on approach chosen)
**Target Date:** Before soft launch (late February 2026)
### Success Metrics
- Withstands common DDoS attacks (volumetric, SYN floods)
- 99.9%+ uptime during normal operations
- < 1 hour maintenance per month
- Zero "midnight emergency" pages
### Fallback Plan
If Phase 1 protection proves inadequate:
- Cloudflare Spectrum as immediate mitigation
- Re-evaluate threat model
- Consider managed DDoS services
- Iterate rather than over-engineer
---
## 📅 IMPLEMENTATION TIMELINE
### February 2026 (Month 1) - FOUNDATION
**Week 1 (Feb 8-14):**
- ✅ Phase 0.5 Services 1-3 deployed (Gitea, Uptime Kuma, MkDocs)
-Automation system operational
- ⏳ Services 4-5 deploying (Wiki.js, NextCloud)
- ⏳ Complete three-tier documentation architecture
**Week 1 (Feb 8-11) — COMPLETED:**
- ✅ Phase 0.5 Services 1-5 deployed (Gitea, Uptime Kuma, MkDocs, Automation, Code-Server)
-TX1 allocation fix (6 game servers recovered)
- ✅ Game server monitoring added (12 monitors)
- ✅ ATM10 memory fix (16GB → 20GB)
- ✅ Infrastructure Manifest v1.5
- ✅ Session handoff v2.0 + TASKS v2.0
**Week 2 (Feb 15-21):**
- Deploy Netdata (analytics.firefrostgaming.com)
- Deploy Vaultwarden (vault.firefrostgaming.com)
- Complete Phase 0.5 (100% - 5/5 services)
- Begin Phase 1: Simplified DDoS protection
**Week 2 (Feb 12-15):**
- [ ] Deploy NextCloud (downloads.firefrostgaming.com)
- [ ] Deploy Wiki.js (subscribers + staff)
- [ ] Update remaining documentation
- [ ] FoundryVTT subdomain setup
**Week 3-4 (Feb 22 - Mar 7):**
- Paymenter billing integration
- Subscriber portal testing
- Staff documentation creation
- Soft launch preparation
**Week 3-4 (Feb 16 - Mar 1):**
- [ ] Soft launch to existing community (3 members)
- [ ] Phase 1: Simplified DDoS protection
- [ ] Paymenter billing integration
- [ ] Subscriber workflow testing
### March 2026 (Month 2) - SOFT LAUNCH
**Weeks 1-2:**
- Soft launch to existing community (3 members)
- Soft launch to existing community
- Test subscriber workflow end-to-end
- Validate world download process
- Gather feedback, iterate
**Weeks 3-4:**
- Public announcement preparation
- Content creation (public docs)
- Social media setup (Meg's domain)
- Discord structure finalization
### April-June 2026 (Months 3-5) - PUBLIC LAUNCH
**April:**
- Public launch
- Social media campaigns
- Public launch, social media campaigns
- Recruit first 20 subscribers
- Monitor Phase 1 auth (manual)
**May:**
- Evaluate Phase 2 auth automation trigger
- Staff recruitment (builders, social media)
- Begin LuckPerms implementation
**June:**
- Reach 50 subscribers (target)
- Deploy Phase 2 auth if needed
- LuckPerms implementation
- Website v1.0 launch
- Reach 50 subscribers target
### July-December 2026 (Months 6-12) - GROWTH & REFINEMENT
### July-December 2026 (Months 6-12) - GROWTH
**Ongoing:**
- Scale infrastructure as needed
- Add new modpacks based on votes
- Iterate on subscriber experience
- Meg's social media campaigns
- Community events (Fire vs Frost competitions)
---
@@ -457,61 +378,54 @@ If Phase 1 protection proves inadequate:
## 🛠️ TECHNICAL DEBT & IMPROVEMENTS
### Immediate Priorities (Next 7 Days)
1. **Complete Phase 0.5** (Services 4-5)
2. **Test subscriber workflow** end-to-end
3. **Document staff SOPs** in staff Wiki
4. **Webhook setup** for MkDocs auto-rebuild
1. Deploy NextCloud (three use cases ready)
2. Deploy Wiki.js (subscribers + staff)
3. Update FIREFROST-PROJECT-SCOPE-V2.md (THIS UPDATE)
4. FoundryVTT subdomain
### Short-Term (Next 30 Days)
1. **Netdata deployment** (analytics)
2. **Vaultwarden deployment** (password manager)
3. **LuckPerms MySQL** backend (centralized permissions)
4. **World backup automation** (monthly snapshots)
1. Frostwall (UFW) deployment on game servers
2. LuckPerms MySQL backend
3. World backup automation
4. ATM10 scheduled restart (if leak persists)
### Medium-Term (Next 90 Days)
1. **Phase 2 Authentication** (webhook automation)
2. **Website v1.0** (firefrostgaming.com)
3. **Staff recruitment** (2-3 builders, 1 social media)
4. **Pterodactyl extensions** (Discord integration)
1. Phase 2 Authentication (webhook automation)
2. Website v1.0 (firefrostgaming.com)
3. Staff recruitment
4. Pterodactyl extensions (Discord integration)
### Long-Term (6-12 Months)
1. **Phase 3 Authentication** (SSO) if needed
2. **Custom modpack development**
3. **API for external integrations**
4. **Mobile app** (subscriber portal)
1. Phase 3 Authentication (SSO) if needed
2. Custom modpack development
3. API for external integrations
4. Mobile app (subscriber portal)
---
## 📊 SUCCESS METRICS
### Technical Metrics
- **Uptime:** >99.5% (tracked via Uptime Kuma)
- **Uptime:** >99.5% (tracked via Uptime Kuma — 17 monitors)
- **Response Time:** <100ms (Nginx)
- **TPS (Game Servers):** Stable 20.0
- **Automation Success Rate:** >95%
### Business Metrics
- **Month 1:** 3 subscribers (soft launch)
- **Month 3:** 20 subscribers (public launch)
- **Month 6:** 50 subscribers
- **Month 12:** 100+ subscribers
**Revenue Targets:**
### Revenue Targets
- Month 1: $15/month (validation)
- Month 3: $100/month (break-even operations)
- Month 3: $100/month (break-even)
- Month 6: $250/month (sustainable)
- Month 12: $500+/month (growth mode)
- Month 12: $500+/month (growth)
### Community Metrics
- **Discord Activity:** Daily active users
- **Fire vs Frost Balance:** 45-55% split (competitive balance)
- **Fire vs Frost Balance:** 45-55% split
- **Subscriber Retention:** >80% monthly
- **Support Response Time:** <24 hours
@@ -522,13 +436,14 @@ If Phase 1 protection proves inadequate:
### Medical Accessibility
**Michael's Limitations:**
- Type 1 Diabetes - Jack alerts take absolute priority
- Hand limitations from surgery - all code in small blocks (8-10 lines max)
- Type 1 Diabetes Jack alerts take absolute priority
- Permanent hand nerve damage (March 2025 surgery) — all manual code in small blocks (8-10 lines max)
- Automation system and Code-Server critical for reducing physical strain
- Work sessions must allow for health breaks
- Automation system critical for reducing repetitive tasks
**System Designed Around:**
- One-paste deployments
- One-paste deployments (automation)
- Browser-based editing (Code-Server)
- Self-healing services (systemd)
- Comprehensive documentation for handoffs
- Minimal midnight emergencies
@@ -537,71 +452,61 @@ If Phase 1 protection proves inadequate:
**"Forever Home" Provider:**
- Long-term partnership, not transactional
- Jon Beard (Network Specialist) - primary contact
- Jon Beard (Network Specialist) primary contact
- Trust-based relationship (6+ months)
- Infrastructure decisions made together
**Critical:** Maintain this relationship, communicate proactively
---
## 📖 CURRENT DOCUMENTATION
### Operational Documents (Keep In Root)
### Core Documents (In Git Repository)
1. **FIREFROST-PROJECT-SCOPE-V2.md** (THIS DOCUMENT)
2. **session-handoff.md** - Current status for Claude sessions
3. **workflow-guide.md** - Michael + Claude collaboration process
4. **design-bible-v1.1.md** - Visual identity guide
5. **path-philosophy.md** - Fire vs Frost explained
6. **subscription-tiers-final.md** - Detailed tier breakdown
7. **awakened-gateway.md** - $1 handshake philosophy
8. **provider-communications.md** - Breezehost relationship archive
9. **visual-assets-guide.md** - Asset inventory & usage
10. **server-deletion-policy.md** - World backup policy
**Relationship & Context:**
1. CLAUDE-RELATIONSHIP-CONTEXT.md — Partnership declaration, emotional moments
2. SESSION-TRANSITION-FEB11-2026.md — Comprehensive session handoff
3. session-handoff.md (v2.0) — Current status for Claude sessions
### Deployment Documentation
**Infrastructure & Operations:**
4. FIREFROST-PROJECT-SCOPE-V2.md (THIS DOCUMENT)
5. Firefrost_Infrastructure_Manifest.md (v1.5) — Server IPs, ports, UUIDs
6. workflow-guide.md — Collaboration protocol
7. automation/USAGE.md — Automation system guide
1. **gitea-deployment.md** - Service 1/5 deployment guide
2. **uptime-kuma-deployment.md** - Service 2/5 deployment guide
3. **automation/USAGE.md** - Automation system guide
**Planning & Community:**
8. design-bible-v1.1.md — Visual identity guide
9. path-philosophy.md — Fire vs Frost explained
10. subscription-tiers-final.md — Tier breakdown
11. discord-structure-complete.md — Discord architecture
12. firefrost-master-implementation-plan.md — 12-month roadmap
### Archived (docs/archive/2026-02-09-consolidation/)
- Historical session summaries (Feb 8-9)
- Superseded planning documents
- Old implementation plans
- Planning docs not yet executed
**Deployment Guides:**
13. gitea-deployment.md
14. uptime-kuma-deployment.md
15. mkdocs-deployment.md
16. code-server-deployment.sh
---
## 🎯 THE PATH FORWARD
### This Week (Feb 9-15, 2026)
### This Week (Feb 11-15, 2026)
**Monday (TODAY):**
- [x] Consolidate documentation (this document)
- [ ] Complete Services 4-5 (Wiki.js, NextCloud)
- [ ] Test subscriber workflow
- [ ] Create staff documentation structure
**Completed:**
- [x] Fix TX1 allocations (6 servers recovered)
- [x] Add game server monitoring (12 monitors)
- [x] Update Infrastructure Manifest v1.5
- [x] Rewrite session-handoff.md v2.0
- [x] Rewrite TASKS.md v2.0
- [x] Update FIREFROST-PROJECT-SCOPE-V2.md (this document)
**Tuesday-Wednesday:**
- [ ] Deploy Netdata (Service 6 - analytics)
- [ ] Deploy Vaultwarden (Service 7 - passwords)
- [ ] Complete Phase 0.5 (100%)
**Thursday-Friday:**
- [ ] Staff SOPs written in staff Wiki
- [ ] World backup automation script
- [ ] Subscriber onboarding checklist
**Weekend:**
- [ ] Test complete subscriber experience
- [ ] Document any issues
- [ ] Prepare for soft launch
**Remaining:**
- [ ] Deploy NextCloud
- [ ] Deploy Wiki.js (subscribers + staff)
- [ ] Extract staff.zip (images → Git, videos → NextCloud)
- [ ] FoundryVTT subdomain
### Next Week (Feb 16-22, 2026)
- Soft launch to existing community
- Iterate based on feedback
- Begin Phase 1 (Simplified DDoS)
@@ -613,10 +518,7 @@ If Phase 1 protection proves inadequate:
**This document is the single source of truth.**
When in doubt about priorities, architecture decisions, or project scope, refer to this document. All other documents are either:
- Historical (archived)
- Operational guides (specific technical details)
- Future planning (not yet prioritized)
When in doubt about priorities, architecture decisions, or project scope, refer to this document.
**Update Schedule:**
- Minor updates: As needed (via Git)
@@ -625,217 +527,17 @@ When in doubt about priorities, architecture decisions, or project scope, refer
**Document Owner:** Michael "Frostystyle" Krause
**Last Major Update:** February 9, 2026 - Post-automation deployment, pre-subscriber portal launch
---
**Fire + Frost = Where Passion Meets Precision** 🔥❄️
*Built for marathon sessions. Designed for accessibility. Optimized for growth.*
---
## 🖥️ CODE-SERVER DEPLOYMENT (ACCESSIBILITY ENHANCEMENT)
## Revision History
**Added:** February 10, 2026
**Priority:** HIGH - Addresses hand limitations directly
### The Problem
**Current workflow requires:**
- SSH terminal access
- Command-line file editing
- Manual Git commands
- Difficult on mobile devices
- Challenging with hand nerve damage
**Michael spends significant time:**
- Copy/pasting command blocks
- Managing SSH sessions
- Navigating terminal editors
- Executing Git workflows
### The Solution: Code-Server
**What:** Browser-based Visual Studio Code
**Where:** code.firefrostgaming.com (Command Center VPS)
**Impact:** Eliminates 90% of terminal work for documentation
**Key Features:**
- Full VS Code experience in browser
- Visual file explorer (point and click)
- Git GUI (no commands needed)
- Markdown preview
- Works on any device (Chromebook, phone, tablet)
- Enables Meg to edit docs without SSH knowledge
### Implementation Plan
**Service Details:**
- URL: code.firefrostgaming.com
- Location: Command Center (63.143.34.217)
- Port: 8080 (internal, Nginx proxy)
- Auth: Password (Authentik SSO in Phase 2)
- SSL: Let's Encrypt
**Deployment Time:** 1-2 hours
**Workflow After Deployment:**
1. Open code.firefrostgaming.com in browser
2. Enter password
3. Navigate files visually
4. Edit with full GUI
5. Commit via Source Control tab
6. Push with one click
**No SSH needed for documentation work!**
### Benefits
**For Michael (The Wizard):**
- ✅ Reduces hand strain significantly
- ✅ Works on Chromebook + S24 Ultra
- ✅ Visual Git workflow
- ✅ No micro-block commands for file edits
- ✅ Can work from any device
**For Meg (The Emissary):**
- ✅ Can edit docs without SSH
- ✅ User-friendly interface
- ✅ Visual file management
- ✅ No command-line knowledge needed
**For The Project:**
- ✅ Faster documentation updates
- ✅ Lower barrier for contributions
- ✅ Mobile-friendly workflow
- ✅ Future: Team members can contribute
### Phase Integration
**Phase 0.5 Extension:**
- Code-Server deployment (this week)
- Basic password authentication
- Essential VS Code extensions
**Phase 2 Enhancement:**
- Authentik SSO integration
- Fire + Frost custom theme
- Shared editing capabilities
**Phase 3 Advanced:**
- Live collaboration
- Mobile PWA
- Custom workspace configurations
### Success Metrics
- ✅ HTTPS access working
- ✅ File editing smooth on desktop
- ✅ File editing smooth on mobile
- ✅ Git operations via GUI work
- ✅ Michael's terminal time reduced 90%
- ✅ Meg successfully edits docs
### Documentation
**Deployment Plan:** docs/code-server-deployment-plan.md
**Post-Deployment:** docs/code-server-deployment.md (created after)
---
**This is a MAJOR accessibility win for The Wizard!** 🧙‍♂️✨
---
## PHASE 0.5 CLARIFICATION (Feb 11, 2026)
**Core Services: 5/5 COMPLETE**
1. ✅ Gitea
2. ✅ Uptime Kuma
3. ✅ MkDocs
4. ✅ Wiki.js Staff
5. ✅ Wiki.js Subscribers
**Additional Services (Moved to Phase 0.6):**
6. ⏳ Netdata (analytics.firefrostgaming.com)
7. ⏳ Vaultwarden (vault.firefrostgaming.com)
**Why the split:** Core documentation infrastructure (5 services) is complete. Monitoring and security tools (2 services) moved to separate phase to clarify completion status.
**Next Priority:** Code-Server deployment (accessibility enhancement for Michael's hand limitations)
---
## 📅 **FEBRUARY 11, 2026 UPDATE**
### **Phase 0.5+ Complete: Code-Server**
**Service:** Browser-based VS Code
**Domain:** code.firefrostgaming.com
**IP:** 74.63.218.202 (Command Center VPS)
**Purpose:** Mobile editing workflow, 90% reduction in SSH dependency
**Status:** ✅ OPERATIONAL (Feb 11, 2026)
**Accessibility Impact:**
- Michael's hand limitations accommodated
- Edit files from ANY device (phone, tablet, Chromebook)
- No SSH terminal needed for documentation work
- Perfect for marathon sessions
### **Phase 0.6 Timeline Adjusted: NextCloud Tonight**
**Original Plan:** Deploy in 2-3 weeks
**New Plan:** Deploy TONIGHT (Feb 11, 2026)
**Reason for Acceleration:**
1. Consultant video archive (2.2GB) - Meg needs web access
2. Holly's Pokerole project - future file delivery
3. Subscriber world downloads (planned use case)
**Three use cases converged → deploy once, solve three problems**
### **Friend Assistance in Action: Holly's Pokerole Project**
**Project:** Aurelian Pokédex (115 custom Pokémon for Pokerole TTRPG)
**Friend:** Holly (Newfoundland, Canada)
**Infrastructure Provided:**
- Gitea repos (pokerole-project org)
- Future FoundryVTT module hosting
**Timeline:** 2-4 weeks (Tier 1 complete, Tier 3 in progress)
**Impact on Firefrost:** Minimal - validates infrastructure, no new services
**Protocol Evaluation:** ✅ Perfect fit (uses existing, teaches to fish, no burden)
**Benefit to Firefrost:**
- Multi-user Gitea tested before subscribers
- Collaboration workflows validated
- Friend Assistance Protocol proven in practice
### **The Consultant Photo Archive**
**Archive Size:** 2.2GB (images + videos)
**Timeline:** 2016-2025 (9 years)
**Status:** Uploaded Feb 11, awaiting extraction
**The Five Consultants Documented:**
- 🐺 Jack (Diabetic Alert Dog - medical partner)
- 🐕 Oscar (Adopted Halloween 2020 - found his home)
- 🐕 Jasmine (Meg's 100-lb guardian)
- 🐱 Butter (CEO since Nov 19, 2016 - 8+ years ruling)
- 🐱 Noir (The Shadow - watches and knows)
**Why This Matters:**
This is the FAMILY that built Firefrost Gaming. When children inherit the project, they'll know the Consultants who were there from the beginning.
**Documentation Created:**
- consultant-photo-archive.md (complete bios, timelines, adoption stories)
- Archive organization: images in Git, videos in NextCloud, sorted by year
---
**Updated:** February 11, 2026 4:30 PM CST
**Next Update:** After tonight's deployments (NextCloud + FoundryVTT diagnostic + staff.zip extraction)
| Version | Date | Changes |
| :---- | :---- | :---- |
| 2.0 | 2026-02-09 | Initial V2 scope document. Post-automation deployment, pre-subscriber portal launch. |
| 2.1 | 2026-02-11 | Updated to current state. Corrected game server lists (12 total, NC1 all on single IP). Added Code-Server as Service 5. Updated monitoring (17 monitors). TX1 allocation fix documented. ATM10 memory fix noted. Timeline updated with Week 1 completions. Documentation list updated. Removed stale references. |