Rewrite TASKS.md v2.0 - Current priorities, Feb 11 accomplishments

This commit is contained in:
Firefrost Automation
2026-02-11 19:20:54 -06:00
parent 01e291128b
commit 5ea97828a7

View File

@@ -1,345 +1,176 @@
# FIREFROST GAMING - TASKS & PROGRESS TRACKER
# 🔥❄️ FIREFROST GAMING - CURRENT TASKS & PRIORITIES
**Last Updated:** February 9, 2026
**Current Focus:** Phase 0.5 - Management Services Deployment
**Last Updated:** February 11, 2026
**Version:** 2.0
**Updated By:** Michael + Claude
---
## 📊 PHASE 0.5 PROGRESS: 60% COMPLETE (3/5 Services)
## ✅ COMPLETED TODAY (Feb 11, 2026)
### ✅ Completed Services
### TX1 Game Server Recovery
- All 6 TX1 servers were DOWN (bound to wrong IP: 38.68.14.188 instead of 38.68.14.26-30)
- Root cause: Pterodactyl allocations pointed to Billing VPS IP
- Fix: Allocated correct port ranges (25565-25580, 5520-5521, 30000) to correct IPs
- Assigned each server to correct IP:port combo
- All 6 servers restarted and verified operational
- **Lesson learned: "I would have known earlier if game servers were in Uptime Kuma"**
**Service 1/5: Gitea** (git.firefrostgaming.com)
- Status: DEPLOYED Feb 8, 2026
- IP: 74.63.218.202
- Purpose: Git repository for all infrastructure
- SSL: Active (Let's Encrypt)
- GitHub Mirror: Configured (auto-sync)
### Game Server Monitoring Added
- 12 game server monitors added to Uptime Kuma (TCP Port type)
- 6 TX1 Dallas + 6 NC1 Charlotte
- Total monitors now: 17 (5 infrastructure + 12 game servers)
- NC1 routing resolved — reachable from Command Center
**Service 2/5: Uptime Kuma** (uptime.firefrostgaming.com)
- Status: DEPLOYED Feb 9, 2026
- IP: 74.63.218.203
- Purpose: Infrastructure monitoring
- SSL: Active (Let's Encrypt)
- Discord: Integrated (#network-status)
### FoundryVTT Verified
- Configuration reviewed and confirmed correct
- Running on 38.68.14.26:30000
- Holly can use it for Pokerole campaign
- Subdomain setup (foundry.firefrostgaming.com) deferred to later
**Service 3/5: MkDocs** (docs.firefrostgaming.com)
- Status: DEPLOYED Feb 9, 2026
- IP: 74.63.218.204
- Purpose: PUBLIC documentation (Git-native)
- SSL: Active (Let's Encrypt)
- Theme: Material with search enabled
### ATM10 Memory Fix
- Was at 98.6% memory (15.78/16 GiB) with 1.9GB memory leak
- Bumped allocation from 16GB to 20GB
- Restarted — now at 63% (12.55/20 GiB) with headroom
- Monitor for leak recurrence; may need scheduled restarts
### ⏳ Pending Services
### Infrastructure Manifest Updated
- v1.5 committed to Git
- Corrected NC1 server list (all on single IP with unique ports)
- Corrected TX1 server list
- Updated UUIDs from actual Panel data
- Added Code-Server to management services
**Service 4/5: Wiki.js** (subscribers.firefrostgaming.com + staff.firefrostgaming.com)
- Status: NEXT - Ready to deploy
- IP: 74.63.218.205
- Purpose: SUBSCRIBER + STAFF documentation portals
- Auth: Manual Phase 1, webhook automation Phase 2
**Service 5/5: NextCloud** (downloads.firefrostgaming.com)
- Status: PLANNED
- IP: 74.63.218.206
- Purpose: World downloads for subscribers
- Retention: 30-day (90-day for Ascendant+)
### Session Handoff Rewritten
- v2.0 — clean, no duplicates, current state
- First file edited and committed via Code-Server!
---
## 🔧 TROUBLESHOOTING TASKS
## ⏳ IMMEDIATE PRIORITIES
### GitHub Mirror Access Issue
**Priority:** Medium
**Status:** ✅ RESOLVED
**Created:** Feb 9, 2026 1:15 PM CST
**Resolved:** Feb 9, 2026 1:35 PM CST
### 1. Update FIREFROST-PROJECT-SCOPE-V2.md
- **Priority:** HIGH
- **Reason:** Master scope doc needs to reflect current state
- **Changes needed:** Game server lists, Phase 0.5+ status, Code-Server added
**Root Cause:**
Claude's security model requires at least ONE URL from a repository to be "user-provided" before accessing other files in that repo.
### 2. Update TASKS.md
- **Priority:** HIGH
- **Status:** THIS UPDATE (you're reading it)
**Solution:** Repository Unlock Method
1. User pastes ONE raw GitHub URL from the repository
2. This "unlocks" the entire repository for Claude
3. Claude can now fetch ANY file from that repo automatically
4. No more URL pasting needed for that repository!
### 3. Deploy NextCloud (downloads.firefrostgaming.com)
- **Priority:** HIGH
- **Location:** Ghost VPS (64.50.188.14)
- **Use cases:** Consultant video archive (Meg), Holly's project files, subscriber world downloads
- **Three use cases = deploy now**
**Test Results:**
- Repository visibility: PUBLIC ✅
- First URL provided: provider-communications.md ✅
- Subsequent files accessible without pasting: session-handoff.md ✅, TASKS.md ✅
- Repository fully unlocked: ALL 28+ docs accessible ✅
### 4. FoundryVTT Subdomain
- **Priority:** MEDIUM
- **Task:** Set up foundry.firefrostgaming.com with SSL via Nginx reverse proxy
- **Currently:** Accessible via IP:port only (38.68.14.26:30000)
**Actual Workflow (Even Better Than Expected):**
1. Michael pastes ONE raw GitHub URL from the repo (one-time unlock)
2. Claude can now read ANY file from that repo automatically
3. Zero additional URL pasting needed
**Benefits:**
- ONE paste unlocks entire repository (28+ files)
- Saves Michael's hands (no bash commands needed)
- Fast documentation access
- Works perfectly with automation system
**Repository Unlocked:**
- https://github.com/Frostystyle/firefrost-operations-manual (FULL ACCESS)
### 5. ATM10 Restart Schedule
- **Priority:** MEDIUM
- **Task:** Consider daily/every-other-day scheduled restarts to prevent memory leak buildup
- **Monitor:** Watch memory usage over next few days
---
## 📋 INFRASTRUCTURE TASKS
## 📋 PHASE 0.5+ STATUS
### TX1 ↔ NC1 Communication Issue
**Priority:** Medium
**Status:** TICKET SENT TO BREEZEHOST
**Created:** Feb 9, 2026 1:10 PM CST
### Completed Services
**Issue:**
TX1 Dallas and NC1 Charlotte cannot communicate directly. Dallas gateway returns "Destination Net Unreachable" immediately. Charlotte can route toward Dallas but packets timeout after 9 hops.
| # | Service | Domain | Location | Date |
| :---- | :---- | :---- | :---- | :---- |
| 1 | Gitea | git.firefrostgaming.com | Command Center | Feb 8-9 |
| 2 | Uptime Kuma | status.firefrostgaming.com | Command Center | Feb 9 |
| 3 | MkDocs | docs.firefrostgaming.com | Ghost VPS | Feb 9 |
| 4 | Code-Server | code.firefrostgaming.com | Command Center | Feb 11 |
| 5 | Automation | N/A (daemon) | Command Center | Feb 9 |
**Diagnostic Results:**
- TX1 → NC1: Complete failure at gateway (38.68.14.25 !N)
- NC1 → TX1: 9 hops through backbone, then timeout
- Firewall: Not blocking (no UFW rules for 216.239.x)
- Conclusion: Datacenter-level routing isolation
### Pending Services
**Ticket Sent:**
Asked Breezehost if this is:
1. Known limitation between Dallas/Charlotte datacenters
2. Solvable with inter-DC routing configuration
3. Acceptable to implement VPN tunnel (WireGuard/OpenVPN) if needed
**Waiting On:** Breezehost response (Jon/Ryan/Brandon)
**Business Impact (If No Solution):**
- Cannot implement BungeeCord/Velocity proxy
- Cannot use centralized database architecture
- Cannot do direct server-to-server backups
- Must design around datacenter isolation
| # | Service | Domain | Location | Priority |
| :---- | :---- | :---- | :---- | :---- |
| 6 | NextCloud | downloads.firefrostgaming.com | Ghost VPS | HIGH |
| 7 | Wiki.js (Subscribers) | subscribers.firefrostgaming.com | Ghost VPS | MEDIUM |
| 8 | Wiki.js (Staff) | staff.firefrostgaming.com | Ghost VPS | MEDIUM |
| 9 | Vaultwarden | vault.firefrostgaming.com | TBD | LOW |
| 10 | Netdata | analytics.firefrostgaming.com | TBD | LOW |
---
## 🚀 AUTOMATION SYSTEM
## 🛡️ PHASE 1: DDoS PROTECTION (PLANNING)
### Firefrost Automation Framework
**Status:** ✅ FULLY OPERATIONAL
**Deployed:** Feb 9, 2026
**Efficiency Gain:** 95% reduction in manual operations
**Key Benefits:**
- Michael pastes ONE command to queue tasks
- Daemon executes automatically (10s polling)
- Results auto-commit to Git
- Claude reads results from GitHub mirror
- Perfect for marathon sessions with hand limitations
**Usage:**
- Start daemon: `nohup bash automation/automation-daemon.sh > /dev/null 2>&1 &`
- Queue tasks: `cat > automation/queue/task-name.sh << 'EOF' ... EOF`
- Read results: https://raw.githubusercontent.com/.../automation/results/
- **Status:** Planning phase — deploy after Phase 0.5 completion
- **Options:** Cloudflare Spectrum, Simplified GRE, or Hybrid
- **Decision point:** Design session after management services complete
- **Target:** Before soft launch (late February 2026)
---
## 📝 DOCUMENTATION UPDATES NEEDED
## 🔧 INFRASTRUCTURE MAINTENANCE
### After This Session
- [ ] Update FIREFROST-PROJECT-SCOPE-V2.md (GitHub unlock solution)
- [ ] Update workflow-guide.md (New documentation access method)
- [ ] Re-upload updated project files to Claude Project
### Frostwall (UFW) Deployment
- **Status:** Not yet deployed on game servers
- **Priority:** After Phase 0.5 services complete
- **Scope:** TX1 + NC1 game server firewall rules
### Regular Maintenance
- Monitor ATM10 memory leak
- Check SSL certificate renewals (certbot)
- Review Uptime Kuma alerts
- Git repository housekeeping
---
## 🎯 NEXT PRIORITY: WIKI.JS DEPLOYMENT
## 📚 DOCUMENTATION DEBT
**Target:** Complete Services 4-5 today (Feb 9, 2026)
**Method:** Use automation system (one paste per service)
**Goal:** Reach 100% Phase 0.5 completion
### Files Needing Updates
- FIREFROST-PROJECT-SCOPE-V2.md (game server lists, Phase status)
- workflow-guide.md (add Code-Server workflow, GitHub URL workflow)
- CLAUDE-RELATIONSHIP-CONTEXT.md (add Feb 11 session context)
### Files Recently Updated
- ✅ Firefrost_Infrastructure_Manifest.md (v1.5 - Feb 11)
- ✅ session-handoff.md (v2.0 - Feb 11)
- ✅ TASKS.md (v2.0 - Feb 11, this file)
---
**END OF TASKS.md**
## 🎯 UPCOMING MILESTONES
### This Week (Feb 11-15)
- [x] Fix TX1 allocations
- [x] Add game server monitoring
- [x] Update Infrastructure Manifest
- [x] Rewrite session-handoff.md
- [x] Update TASKS.md
- [ ] Update FIREFROST-PROJECT-SCOPE-V2.md
- [ ] Deploy NextCloud
- [ ] Extract staff.zip (images → Git, videos → NextCloud)
### Next Week (Feb 16-22)
- [ ] Soft launch to existing community (3 members)
- [ ] Begin Phase 1 DDoS planning
- [ ] Social media setup (Meg)
- [ ] FoundryVTT subdomain
### This Month (February)
- [ ] Complete all pending management services
- [ ] Frostwall deployment
- [ ] Subscriber workflow testing
- [ ] Staff documentation creation
---
## 🎨 FUTURE ENHANCEMENTS
## Revision History
### Landing Pages for Subscriber & Staff Portals
**Priority:** Medium
**Status:** PLANNED
**Created:** Feb 9, 2026 1:45 PM CST
**Goal:**
Create landing pages for staff.firefrostgaming.com and subscribers.firefrostgaming.com root domains that serve as entry points to multiple tools/services.
**Current State (Phase 1):**
- Root domains auto-redirect to /codex (Wiki.js)
- Users go straight to documentation
- Simple, functional, gets us operational
**Future State (Phase 2):**
- Custom landing pages at root (`/`)
- Links to multiple services:
- 📖 The Codex (Wiki.js documentation)
- 🔧 Tools (future staff tools)
- 📊 Dashboard (future analytics/status)
- 📥 Downloads (NextCloud for subscribers)
- Secure access control (authenticate at landing page level)
**Design Considerations:**
- Fire/Frost visual identity (match Design Bible)
- Role-based content (subscribers see different options than staff)
- Mobile-responsive
- Fast load times
- SSO/authentication strategy (Phase 2 webhook automation)
**Security Requirements:**
- Authentication BEFORE accessing any services
- Session management
- Secure token handling
- Rate limiting on login attempts
**Technologies to Explore:**
- Static HTML + Tailwind CSS (simple, fast)
- Next.js (if we want dynamic content)
- Authentik or Authelia (SSO/authentication layer)
- Integration with Paymenter subscriber validation
**Next Steps:**
1. Complete Wiki.js deployment (Service 4)
2. Complete NextCloud deployment (Service 5)
3. Reach 100% Phase 0.5 completion
4. THEN discuss landing page architecture in dedicated session
**Discussion Topics for Future Session:**
- Authentication strategy (Phase 1 manual vs Phase 2 webhooks)
- Visual design (Frost vs Fire styling for each portal)
- Navigation structure (what tools/links appear on each portal)
- Mobile vs desktop experience
- Onboarding flow for new subscribers
| Version | Date | Changes |
| :---- | :---- | :---- |
| 1.0 | 2026-02-09 | Initial TASKS.md created |
| 2.0 | 2026-02-11 | Complete rewrite. Added Feb 11 accomplishments (TX1 fix, monitoring, ATM10, manifest, handoff rewrite). Updated Phase 0.5+ status. Current priorities. Documentation debt tracked. |
---
### Configure Wiki.js Git Sync with Gitea
**Priority:** High
**Status:** PENDING - Deploy Wiki.js first
**Created:** Feb 9, 2026 2:00 PM CST
**Goal:**
Set up two-way Git synchronization between Wiki.js and Gitea for markdown-based documentation workflow.
**Prerequisites:**
- ✅ Wiki.js deployed and configured
- ⏳ Admin account created (mkrause612@gmail.com / Butter2018!!)
- ⏳ Initial setup wizard completed
**Implementation Steps:**
1. Create new Gitea repository: `firefrost-codex`
2. Initialize with folder structure:
- `/subscribers/` - Subscriber-facing guides
- `/staff/` - Internal procedures and planning
3. Configure Wiki.js Git sync:
- Repository URL: https://git.firefrostgaming.com/firefrost-gaming/firefrost-codex.git
- Authentication: Git credentials or SSH key
- Sync mode: Two-way (Git ↔ Wiki.js)
- Sync interval: Every 5 minutes or manual trigger
4. Test workflow:
- Create page in Wiki.js → Verify appears in Git
- Create markdown file in Git → Verify appears in Wiki.js
5. Set up path-based permissions:
- Subscribers group: Read-only access to /subscribers/
- Staff group: Full access to /staff/
- Admin group: Full access everywhere
**Benefits:**
- Write in markdown (terminal/editor) OR web UI (Meg's preference)
- All content version controlled in Git
- Automatic sync both directions
- Perfect for Fire + Frost workflow (technical precision + creative editing)
**Next Steps:**
1. Wait for Wiki.js deployment to complete
2. Complete web setup wizard
3. Execute this configuration task
---
---
## 🖥️ CODE-SERVER DEPLOYMENT (NEW - Feb 10, 2026)
**Priority:** HIGH - Accessibility Enhancement
**Impact:** 90% reduction in terminal work for documentation
**Estimated Time:** 1-2 hours
### Pre-Deployment
- [ ] Create DNS A record: code.firefrostgaming.com → 63.143.34.217
- [ ] Verify port 8080 available
- [ ] Check disk space (need ~500MB)
- [ ] Backup Git repo state
### Installation & Configuration
- [ ] Install Code-Server via official script
- [ ] Configure config.yaml (bind 127.0.0.1:8080)
- [ ] Set strong password
- [ ] Create systemd service
- [ ] Enable auto-start on boot
### Network & Security
- [ ] Create Nginx reverse proxy config
- [ ] Enable WebSocket support
- [ ] Obtain SSL certificate (certbot)
- [ ] Configure UFW firewall rules
- [ ] Test HTTPS access
### Post-Deployment
- [ ] Install VS Code extensions (Markdown, Git Graph, GitLens)
- [ ] Configure workspace settings
- [ ] Test file editing
- [ ] Test Git operations
- [ ] Test from Chromebook
- [ ] Test from Samsung S24 Ultra
- [ ] Add to Uptime Kuma monitoring
- [ ] Train Meg on usage
### Documentation
- [ ] Create deployment guide (code-server-deployment.md)
- [ ] Update session-handoff.md
- [ ] Commit all changes to Git
---
**Why This Matters:**
- Browser-based editing = no SSH needed
- Works on mobile devices
- Reduces hand strain significantly
- Enables Meg to contribute without terminal knowledge
**Fire + Frost = Where Passion Meets Precision** 🔥❄️
## ✅ COMPLETED (Feb 11, 2026)
- [x] All 5 Consultant profiles complete (609 lines)
- [x] Staff Wiki structure created with department folders
- [x] Public-safe Consultant profiles for content creation
- [x] Wiki.js deployment documented (Feb 10 recovery)
- [x] Phase 0.5: 100% complete (5/5 services)
- [x] Partnership document verified and tested
- [x] session-handoff.md updated with relationship pointer
## 🎯 NEXT PRIORITY
**Code-Server Deployment:**
- [ ] Deploy Code-Server on Command Center VPS
- [ ] Configure code.firefrostgaming.com
- [ ] Enable browser-based editing
- [ ] Test mobile workflow (Z Flip 6)
- [ ] Create deployment documentation
**Why Next:** Direct accessibility benefit for Michael's hand limitations. Reduces SSH dependency by 90%.
**Fire + Frost = Where Passion Meets Precision** 🔥❄️