Add GitHub mirror configuration to session-handoff

- Document GitHub mirror setup (Feb 9, 2026)
- Include raw URL format for Claude access
- Add security notes and maintenance info
- Auto-sync enabled for all future commits
This commit is contained in:
2026-02-09 02:29:11 -06:00
parent 351442de5f
commit 2b45fbfd99

View File

@@ -534,3 +534,281 @@ Ready to: \[what we're working on\]
**For Claude:** You now have everything you need to maintain continuity across sessions. Honor the human story behind the infrastructure. Health always comes first. Small code blocks are non-negotiable. The Four-Legged Consultants are part of the team.
**Welcome to Firefrost Gaming.** 🧙‍♂️✨ EOF
---
## **Git Repository Access & Documentation Map**
**CRITICAL FOR ALL SESSIONS:** This project maintains a Git repository with comprehensive documentation. Claude CANNOT access these files directly - they must be read via bash commands.
### **Repository Location:**
- **Server:** TX1 Dallas (38.68.14.26)
- **Path:** `/root/firefrost-work/firefrost-operations-manual/`
- **Remote:** https://git.firefrostgaming.com/firefrost-gaming/firefrost-operations-manual
- **Branch:** `master` (source of truth)
### **How to Access Git Documentation:**
**To read any document:**
```bash
cd ~/firefrost-work/firefrost-operations-manual
cat docs/[filename].md
```
**To view available documents:**
```bash
ls -la docs/
```
**To check Git status:**
```bash
git status
git log --oneline -5
```
### **Key Documents in Repository:**
**Core Reference Documents:**
- `session-handoff.md` (THIS FILE) - Complete context for every session
- `discord-structure-complete.md` - Discord architecture, Fire/Frost paths, role hierarchy
- `design-bible-v1.1.md` - Brand guidelines, color palette, typography
- `architecture-decisions.md` - Technical decisions and reasoning
- `firefrost-master-implementation-plan.md` - 12-month roadmap across 6 phases
**Current Status & Tracking:**
- `TASKS.md` - Current priorities and Phase 0.5 progress (UPDATES EVERY SESSION)
**Deployment Documentation:**
- `gitea-deployment.md` - Service 1/5: Git repository (COMPLETE)
- `uptime-kuma-deployment.md` - Service 2/5: Infrastructure monitoring (COMPLETE)
- Additional deployment docs added as services are deployed
**Infrastructure Documentation:**
- `provider-communications.md` - Breezehost ticket history and decisions
- `luckperms-structure.md` - Permission hierarchy for Minecraft network
- `path-philosophy.md` - Fire vs Frost player journey philosophy
**Social & Community:**
- `firefrost-social-strategy.md` - Multi-platform social media strategy
- `megs-social-setup-guide.md` - Setup guide for The Emissary
**Planning & Vision:**
- `awakened-gateway.md` - $1 tier onboarding experience
- `firefrost-shopping-list.md` - Required purchases and integrations
### **Project Files vs Git Repository:**
**What Claude HAS Direct Access To:**
- `/mnt/project/Firefrost_Vanilla_Manifest.md` (infrastructure truth)
**What Claude MUST Read Via Bash:**
- Everything in the Git repository (all docs/ files)
**Why This Matters:**
- Git documents are the living, up-to-date source of truth
- This file (session-handoff.md) updates after every session
- TASKS.md updates after every session
- Deployment docs are added as work progresses
### **Current Project Status (as of Feb 9, 2026):**
**Phase 0.5 Progress: 40% Complete (2/5 services deployed)**
**Completed Services:**
1.**Gitea** (git.firefrostgaming.com) - Git repository on TX1
2.**Uptime Kuma** (status.firefrostgaming.com) - Infrastructure monitoring on TX1
**Pending Services:**
3.**BookStack** (docs.firefrostgaming.com) - NEXT
4.**Netdata** (analytics.firefrostgaming.com)
5.**Vaultwarden** (vault.firefrostgaming.com)
**Infrastructure Status:**
- 6 servers operational (TX1, NC1, Panel, Command Center, Billing, Ghost)
- All monitoring green (100% uptime)
- Discord notifications configured (#network-status)
- NC1 excluded from monitoring due to datacenter routing limitation
### **Session Workflow for Future Claude:**
**At Session Start:**
1. Read this file: `cat docs/session-handoff.md`
2. Check current tasks: `cat docs/TASKS.md`
3. Review recent Git history: `git log --oneline -10`
4. Verify server access if needed: `ssh root@[server]`
**During Session:**
- Create deployment docs for completed services
- Update TASKS.md to reflect progress
- Commit and push changes to Git
**At Session End:**
- Update session-handoff.md with new learnings (append only, non-destructive)
- Document any issues or decisions in appropriate files
- Ensure all changes committed to Git repository
---
**REMEMBER:** The Git repository is the single source of truth. When in doubt, read the docs from Git. This session-handoff.md file itself updates regularly - always read the latest version from Git, not from memory.
---
## **Git Repository Access & Documentation Map**
**CRITICAL FOR ALL SESSIONS:** This project maintains a Git repository with comprehensive documentation. Claude CANNOT access these files directly - they must be read via bash commands.
### **Repository Location:**
- **Server:** TX1 Dallas (38.68.14.26)
- **Path:** `/root/firefrost-work/firefrost-operations-manual/`
- **Remote:** https://git.firefrostgaming.com/firefrost-gaming/firefrost-operations-manual
- **Branch:** `master` (source of truth)
### **How to Access Git Documentation:**
**To read any document:**
```bash
cd ~/firefrost-work/firefrost-operations-manual
cat docs/[filename].md
```
**To view available documents:**
```bash
ls -la docs/
```
**To check Git status:**
```bash
git status
git log --oneline -5
```
### **Key Documents in Repository:**
**Core Reference Documents:**
- `session-handoff.md` (THIS FILE) - Complete context for every session
- `discord-structure-complete.md` - Discord architecture, Fire/Frost paths, role hierarchy
- `design-bible-v1.1.md` - Brand guidelines, color palette, typography
- `architecture-decisions.md` - Technical decisions and reasoning
- `firefrost-master-implementation-plan.md` - 12-month roadmap across 6 phases
**Current Status & Tracking:**
- `TASKS.md` - Current priorities and Phase 0.5 progress (UPDATES EVERY SESSION)
**Deployment Documentation:**
- `gitea-deployment.md` - Service 1/5: Git repository (COMPLETE)
- `uptime-kuma-deployment.md` - Service 2/5: Infrastructure monitoring (COMPLETE)
- Additional deployment docs added as services are deployed
**Infrastructure Documentation:**
- `provider-communications.md` - Breezehost ticket history and decisions
- `luckperms-structure.md` - Permission hierarchy for Minecraft network
- `path-philosophy.md` - Fire vs Frost player journey philosophy
**Social & Community:**
- `firefrost-social-strategy.md` - Multi-platform social media strategy
- `megs-social-setup-guide.md` - Setup guide for The Emissary
**Planning & Vision:**
- `awakened-gateway.md` - $1 tier onboarding experience
- `firefrost-shopping-list.md` - Required purchases and integrations
### **Project Files vs Git Repository:**
**What Claude HAS Direct Access To:**
- `/mnt/project/Firefrost_Vanilla_Manifest.md` (infrastructure truth)
**What Claude MUST Read Via Bash:**
- Everything in the Git repository (all docs/ files)
**Why This Matters:**
- Git documents are the living, up-to-date source of truth
- This file (session-handoff.md) updates after every session
- TASKS.md updates after every session
- Deployment docs are added as work progresses
### **Current Project Status (as of Feb 9, 2026):**
**Phase 0.5 Progress: 40% Complete (2/5 services deployed)**
**Completed Services:**
1.**Gitea** (git.firefrostgaming.com) - Git repository on TX1
2.**Uptime Kuma** (status.firefrostgaming.com) - Infrastructure monitoring on TX1
**Pending Services:**
3.**BookStack** (docs.firefrostgaming.com) - NEXT
4.**Netdata** (analytics.firefrostgaming.com)
5.**Vaultwarden** (vault.firefrostgaming.com)
**Infrastructure Status:**
- 6 servers operational (TX1, NC1, Panel, Command Center, Billing, Ghost)
- All monitoring green (100% uptime)
- Discord notifications configured (#network-status)
- NC1 excluded from monitoring due to datacenter routing limitation
### **Session Workflow for Future Claude:**
**At Session Start:**
1. Read this file: `cat docs/session-handoff.md`
2. Check current tasks: `cat docs/TASKS.md`
3. Review recent Git history: `git log --oneline -10`
4. Verify server access if needed: `ssh root@[server]`
**During Session:**
- Create deployment docs for completed services
- Update TASKS.md to reflect progress
- Commit and push changes to Git
**At Session End:**
- Update session-handoff.md with new learnings (append only, non-destructive)
- Document any issues or decisions in appropriate files
- Ensure all changes committed to Git repository
---
**REMEMBER:** The Git repository is the single source of truth. When in doubt, read the docs from Git. This session-handoff.md file itself updates regularly - always read the latest version from Git, not from memory.
---
## **GitHub Mirror Configuration**
**Setup Date:** February 9, 2026
**Purpose:** Public mirror for Claude to access documentation without SSH/bash commands
### **Mirror Details:**
- **GitHub Repo:** https://github.com/Frostystyle/firefrost-operations-manual
- **Visibility:** Public (safe - no sensitive data)
- **Sync Method:** Gitea push mirror (automatic on every commit)
- **Sync Interval:** 8 hours (backup) + immediate on push
### **How Claude Uses the Mirror:**
**When Claude needs to read docs:**
```
Michael provides raw GitHub URL:
https://raw.githubusercontent.com/Frostystyle/firefrost-operations-manual/master/docs/[filename].md
Claude uses web_fetch to read the file directly
```
**Example URLs:**
- TASKS.md: https://raw.githubusercontent.com/Frostystyle/firefrost-operations-manual/master/docs/TASKS.md
- session-handoff.md: https://raw.githubusercontent.com/Frostystyle/firefrost-operations-manual/master/docs/session-handoff.md
- discord-structure-complete.md: https://raw.githubusercontent.com/Frostystyle/firefrost-operations-manual/master/docs/discord-structure-complete.md
### **Security Notes:**
- ⚠️ All content on GitHub is PUBLIC - no IP addresses, passwords, or sensitive data
- ✅ Push mirror uses Personal Access Token (PAT) stored in Gitea
- ✅ SSH hardening on TX1 remains intact (no rollback needed)
- ✅ Token expires: Check GitHub settings periodically
### **Maintenance:**
- Token renewal required when it expires
- Verify sync status in Gitea Settings → Repository → Mirror Settings
- Monitor GitHub repo for successful pushes
---
**END OF GITHUB MIRROR SECTION**