Align blueprint terminology with the canvas UI
The shipped canvas calls any cloneable starting point a "blueprint", both the
shipped ones loaded via "Load blueprint" and a user's own topology published to
the Library for others to clone. The wiki split this as "template" (shipped) vs
"blueprint" (published), which contradicted the UI. Migrate the shipped-starting
-point sense of "template" to "blueprint" across the concept and reference pages,
keeping a private working copy as a "topology". Certificate templates, GitHub
issue templates, and the [[Library and Templates]] wikilink targets are left as
is.
docs: subjective readability and structure pass
Verified subjective improvements across the wiki (clarity, structure, navigation, terminology), no command or fact changes.
docs: document the prefix as the per-range identifier for concurrent ranges
Deploying-a-Range now tells users to give each concurrent range a distinct prefix; the account-global cloud names carry an automatic per-deployment suffix so ranges never collide in one account, in one region or several.
docs: prerelease consistency, readability, and reporting callout
Consistency and readability pass across the wiki (terminology, schema versions, cross-links, provider matrix, grammar). Home prerelease callout now tells users to open an issue and attach the scrubbed logs/deploy-*.log for analysis.
Rename ARTIE/HAVEN to Offense/Defense across the wiki
Drop the not-fully-wired wireguard transport section; jumpbox manages over ssh
Correct export tfvars path and teardown, add manage.sh lifecycle and enterprise notes
Reclassify Azure from preview to roadmap, same status as Proxmox and ESXi
Azure no longer carries a separate "preview" status; it sits with Proxmox and ESXi as
roadmap, not yet supported. Updates the Providers table and matrix, Home, FAQ,
Cloud-Prerequisites, and Deploying-a-Range. Keeps the accurate note that Azure can
allocate a public address today; drops only the "preview" wording and the separate section.
Add Cloud Prerequisites page: permissions and local requirements before deploy
New page covering the two things an operator needs before running deploy.sh: a
cloud identity with permission to create the export's resources (AWS EC2 set with
AmazonEC2FullAccess as the simple path, the auto_stop IAM/Scheduler exception, and
GCP compute.admin plus enabling the Compute Engine API), and the local tools
(terraform, ssh, tar, Python), with AWS CLI and gcloud auth quick-starts and the
CPUS_ALL_REGIONS quota note. Linked from the sidebar, Home, Getting Started,
Deploying a Range, and the FAQ.
docs: multi-user VPN access, deploy logs, and the mode-named briefing
docs: document ports, terraform state, provisioning, and the WireGuard mode
- Providers: an ingress-ports-by-node-kind table derived from the firewall
generators, with egress explained as routing-decided rather than port-restricted.
- Deploying-a-Range: a terraform-state note (local state, no backend, no lock,
per-export state) and a WireGuard-transport section flagged as not fully wired
(the server comes up, but peer generation and the UDP 51820 rule are unbuilt).
- Concepts: how the export provisions, terraform locally then Ansible from the jumpbox.
docs: wiki accuracy, onboarding, and clarity pass
- Azure moved to a preview tier (Home, Providers matrix plus a preview section);
Proxmox and ESXi stay roadmap.
- Getting-Started: a Before you begin prerequisites checklist and PowerShell
env-var forms alongside the bash ones.
- Deploying-a-Range: a billing caution up front, the real teardown command
(terraform -chdir=terraform destroy) with the missing-teardown.sh gap flagged,
plain one-line explanations of tfvars, CIDR, the SSH key, region, GCP project,
the DNS A record, and WSL, and a stronger operator_source_ranges caution.
- Concepts: a cloud-terms glossary and a schema-vs-product version note.
- Providers: a GCP quota and setup section, symmetric with the AWS one.
- Labs: per-lab walkthrough links; Home gains a step 6 to open the walkthrough.
- tone: drop the "not a course to learn them" gatekeeping; small grammar fixes.
docs: add AWS quota and regional planning guidance
Providers gains a quota section (Elastic IPs with the per-range table and the
increase command, vCPUs, Kali Marketplace subscription, key pair name), all
per region. Deploying-a-Range gains a pre-deploy quota checklist.
wiki: add the ssh key step and provider selection to the deploy docs
wiki: update commands for redstackpro compile and validate
add the redStackPRO wiki pages