-
Notifications
You must be signed in to change notification settings - Fork 0
Prompts
github-actions[bot] edited this page Sep 5, 2026
·
1 revision
Use these prompts as operator checklists when planning, deploying, or changing a LegendForge environment.
Ask:
- Which provider best matches my budget, region, and operating style?
- Which hostname and Cloudflare zone will players use?
- Do I want Cloudflare Access in front of Foundry?
- Do I need break-glass SSH, or can I leave it closed?
- How much persistent storage should I allocate for worlds, assets, and backups?
- Which Foundry system will I install after deployment?
Ask:
- Am I using scoped Cloudflare API tokens instead of broad credentials?
- Am I using Foundry account credentials or a timed release URL?
- Is the Foundry admin key long, unique, and randomly generated?
- Am I keeping
config/secrets.auto.tfvarsout of version control?
Ask:
- Did I review the provider-specific deployment guide?
- Did I confirm the variable files point at the correct cloud account and domain?
- Do I understand what resources will be created and their estimated cost?
- Do I have a rollback or destroy path if the first apply is wrong?
Ask:
- Does this system match my current Foundry version?
- Which modules are required for this world?
- Can I test the module stack in a non-production world first?
- Do I need separate worlds or separate deployments for different communities?
Ask:
- Did I back up the current world data?
- Did I snapshot persistent storage?
- Did I record current Foundry, system, and module versions?
- Am I changing Foundry core, system packages, and modules in a controlled order?
Ask:
- Is the problem DNS, tunnel ingress, compute health, container startup, or the application itself?
- Did I check Terraform outputs and deployment health first?
- Do I have recent backups and restore points?
- Am I using the safest available admin path for this provider?
When updating docs or infrastructure, ask:
- Does this keep LegendForge system-agnostic?
- Does this assume D&D-specific behavior where the platform should stay generic?
- Does this preserve security-first defaults?
- Did I update cross-links if I added major documentation?