-
Notifications
You must be signed in to change notification settings - Fork 0
How To
This page collects common operator tasks using the existing repository guidance.
- Choose AWS for broader enterprise patterns and scalability
- Choose Azure for Azure-native RBAC and portal-based operations
- Choose GCP for strong monitoring and managed service integrations
- Choose Hetzner for the single-server hosting with operator-managed recovery
See the Provider Guide.
- Choose a profile from the Provider Guide
- Follow its README and prepare its own required variable files from that deployment directory
- Run
terraform init - Run
terraform plan - Run
terraform apply - Validate outputs and access the Foundry URL
LegendForge does not install rulesets through Terraform.
After infrastructure is live:
- Log in to Foundry
- Install the system package that matches your Foundry version
- Create or restore the world
- Add modules gradually
- Test the world before inviting players
- Keep Foundry core upgrades controlled
- Track which world uses which system and modules
- Validate heavy module stacks in a test world
- Consider separate worlds or separate deployments for very different communities
- Back up before system or module upgrades
Use Systems Manager Session Manager.
Use the configured administrator path or az vmss run-command invoke for the active scale set.
Use gcloud compute ssh with OS Login.
Use SSH directly to the server IP when enabled.
From the provider deployment directory:
terraform state list
terraform outputUse provider-specific resource names when inspecting details with terraform state show.
For AWS/GCP low cost, follow Low-Cost Profiles to use
paused=true after first boot and backup; restore false to resume.
Persistence behavior differs by provider. Review the generated Terraform plan and the provider-specific deployment guide before disabling compute.
For Hetzner, setting:
compute_enabled = falsedeletes the server and managed data volume. It is not a data-preserving pause. Use a manual server power action only after reviewing its billing and Terraform state consequences, and verify an off-server backup before any teardown-like operation. See the Hetzner lifecycle guide.
Before major changes:
- Back up world data
- Snapshot persistent storage
- Record the active Foundry version
- Record system and module dependencies
- Validate in a test world first
- Check Terraform outputs first
- Confirm DNS and Cloudflare Tunnel status
- Confirm the instance or scale set is healthy
- Check container logs
- Check database connectivity only after application health is known