docs: dynamic version badge on Home so it tracks the latest release
46bd4eb
docs: unify python to 3.11 and point the docker pull at :latest
Matches the canvas requires-python and the main repo README. The Getting-Started
quickstart now pulls :latest instead of a pinned version.
13bf6c5
Document teardown --force for an interrupted deploy
An interrupted deploy can leave instances outside terraform state that a plain
teardown cannot remove; manage.sh teardown --force deletes them in the cloud
first, so nothing is left billing.
7e8371b
Document verify.py, rsp-check, and the C2 payload recipe
Deploying a Range gains a "Verify the deployment" section for verify.py (doors and
stack) with pointers to rsp-check and the briefing. Redirectors and Cover Stories
gains the operator payload recipe (callback domain, URI prefix, gating header) and
an on-box "Checking a redirector" section for rsp-check.
a71dca0
Remove Schema version section from Concepts
4e4dabb
Drop schema-version framing from Home status blurbs
8c9dafc
Rename Library and Templates page to Library and Blueprints
5d25846
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.
99f9dfe
Canvas button is Load blueprint, not Load template
The toolbar button was renamed to "Load blueprint" in the shipped canvas; the
wiki still called it "Load template" in three places.
b3930de
docs: subjective readability and structure pass
Verified subjective improvements across the wiki (clarity, structure, navigation, terminology), no command or fact changes.
24d99d7
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.
a53a9dd
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.
0f52082
Rename ARTIE/HAVEN to Offense/Defense across the wiki
86b0518
Drop the not-fully-wired wireguard transport section; jumpbox manages over ssh
64c03e4
Correct export tfvars path and teardown, add manage.sh lifecycle and enterprise notes
97cf66c
Correct the compile step: the Export tab compiles automatically, no Compile button
167bbb1
Add Library and Templates page: templates, save, publish, clone
New page explaining what each button does: templates load as a shipped starting point
(HAVEN locks with Unlock to edit, ARTIE opens editable, loading never touches the shipped
file), Save stores a private copy, Publish offers a read-only blueprint your org can clone,
and cloning makes a private copy. The Library starts empty by default. Linked from the
sidebar, Home, and Getting Started, and corrected the now-stale Blueprints section in Concepts.
7ca1872
Highlight prerelease beta status up front on Home
Add a prominent prerelease/beta callout below the tagline and update the status badge.
46845c3
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.
9330d9e
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.
b30c15c
docs: Concepts uses artie/haven mode names and schema 0.6.0 (was ops/range, 0.4.0)
57a2c6e
docs: correct the C2 teamserver note (generic none, cobalt to roadmap) and the minimalc2 template names
fa1f9a1
docs: multi-user VPN access, deploy logs, and the mode-named briefing
1ea9c6b
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.
fa15e2c
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.
e9c6f6e
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.
f3f6a24
wiki: correct the provider FAQ and complete the Labs listing
FAQ no longer says ranges deploy on any provider: GCP and AWS are tested end to
end, Azure is preview, Proxmox and ESXi are roadmap. Labs adds the missing
templates: minilab, split-horizon and redirector-rollover, and expands minimal-c2.
3656271
wiki: use the chosen wiki header banner
6c61c01
wiki: audit fixes for terminology, RDR001 domain wording, goad-light forest and the MGT example
7cb1cd3
wiki: restyle the Home page with a banner, badges, callouts and tables
4b6847f