55 lines
1.6 KiB
Markdown
55 lines
1.6 KiB
Markdown
|
|
---
|
|
|
|
## Decision: Management Services on TX1 (Not Command Center)
|
|
|
|
**Date:** February 9, 2026
|
|
**Decision:** Deploy Phase 0.5 management services on TX1 Dallas instead of Command Center
|
|
**Status:** IMPLEMENTED
|
|
|
|
### Rationale
|
|
1. TX1 has 32 vCPU, 256GB RAM - currently 99% idle
|
|
2. Simpler networking without Command Center routing
|
|
3. Keeps Command Center clean for future Frostwall v2.0 DDoS protection
|
|
4. Gitea migration to TX1 was seamless - proven success
|
|
|
|
### Command Center Future Role
|
|
Reserved for Phase 1 DDoS protection (GRE hub, Cloudflare integration)
|
|
|
|
---
|
|
|
|
## Known Limitation: NC1 and TX1 Cannot Communicate Directly
|
|
|
|
**Date:** February 9, 2026
|
|
**Status:** PERMANENT INFRASTRUCTURE CONSTRAINT
|
|
|
|
NC1 Charlotte and TX1 Dallas are in different Breezehost datacenters with no direct routing.
|
|
|
|
### Impact
|
|
- Uptime Kuma on TX1 cannot monitor NC1 services
|
|
- NC1 game servers excluded from TX1-based monitoring
|
|
- Cross-datacenter communication requires public internet
|
|
|
|
### Acceptance
|
|
This is standard for multi-datacenter hosting and does not affect normal operations.
|
|
|
|
---
|
|
|
|
## Decision: Three-Tier Documentation Architecture
|
|
|
|
**Date:** February 9, 2026
|
|
**Decision:** Replace single BookStack with three-tier system
|
|
|
|
| Tier | Technology | Domain | Access |
|
|
|------|------------|--------|--------|
|
|
| PUBLIC | MkDocs | docs.firefrostgaming.com | Anyone |
|
|
| SUBSCRIBERS | Wiki.js + NextCloud | subscribers.firefrostgaming.com | Paid |
|
|
| STAFF | Wiki.js | staff.firefrostgaming.com | Staff |
|
|
|
|
### Rationale
|
|
- Security boundaries per tier
|
|
- Git-native public docs (MkDocs)
|
|
- UI-friendly private docs (Wiki.js for Meg)
|
|
- Appropriate tools for each use case
|
|
|