-
Notifications
You must be signed in to change notification settings - Fork 0
Architecture and Security
github-actions[bot] edited this page Sep 5, 2026
·
1 revision
This page summarizes the repository's shared architecture themes across providers.
LegendForge focuses on the same core domains across clouds:
- Compute for Foundry runtime
- Networking and controlled ingress
- Persistent storage
- Secret management
- Monitoring and alerting
- Backup and recovery support
LegendForge favors:
- Cloudflare Tunnel or equivalent controlled ingress
- Minimal public exposure
- Secret isolation in cloud-native stores where possible
- Break-glass access only when necessary
- Backup discipline before risky changes
LegendForge is infrastructure, not a rules implementation.
That means:
- Terraform provisions the hosting layer
- Foundry runs as the application platform
- Systems and modules are installed after deployment
- Documentation should stay useful for many game families
The repository emphasizes:
- Persistent storage for campaign artifacts
- Backup and restore planning
- Safe upgrade workflow expectations
- Documentation as an operator tool
- AWS emphasizes broader infrastructure building blocks and scaling patterns
- Azure emphasizes Azure-native access control and operations
- GCP emphasizes managed observability and managed services
- Hetzner emphasizes simplicity and cost control