Skip to content

docs: update warpgate template README for ares project and new agent structure#234

Merged
l50 merged 1 commit intomainfrom
fix/update-warpgate-readme
Apr 24, 2026
Merged

docs: update warpgate template README for ares project and new agent structure#234
l50 merged 1 commit intomainfrom
fix/update-warpgate-readme

Conversation

@l50
Copy link
Copy Markdown
Contributor

@l50 l50 commented Apr 23, 2026

Key Changes:

  • Refactored README to represent Ares as the primary project, replacing Dreadnode and legacy template descriptions
  • Updated template listings, descriptions, and architecture/platform support for all agents and components
  • Modernized usage, build, and run instructions for new CLI, agent, and GPU templates
  • Revised documentation, support, and project references to point to Ares and current repositories

Changed:

  • Project branding and focus - README title, intro, and overview updated to center on Ares instead of Dreadnode, clarifying the purpose as building Ares red/blue team agents and AMIs
  • Template listings and descriptions - All agent, orchestrator, and GPU image descriptions reworked to match the new Ares agent structure; tables updated for accuracy, platforms, and base images
  • Build badges and CI references - Updated badge URLs and CI workflow links to point to the new ares repository and workflows
  • Usage instructions - Build, validate, and run examples rewritten for new agent images, architectures, and CLI; included GITHUB_TOKEN and AWS credential requirements where needed
  • Directory and template structure - Directory trees and example YAML updated to reflect new agent breakdown and provisioning process
  • Documentation and support links - All project references, support, and contribution links updated to Ares, with outdated/legacy project and GOAD references removed or replaced

Removed:

  • GOAD infrastructure and Ray cluster template sections - All documentation and tables for legacy GOAD Windows AMIs, Ray cluster, and CTF challenge templates removed to focus exclusively on Ares agent and GPU templates
  • Template comparison table - Feature comparison matrix for legacy agents and base images eliminated in favor of concise template descriptions
  • Outdated contributing, support, and related projects sections - Legacy contribution guides, support channels, and unrelated projects removed to streamline documentation and avoid confusion

@dreadnode-renovate-bot dreadnode-renovate-bot Bot added the area/templates Changes made to warpgate template configurations label Apr 23, 2026
…d details

**Changed:**

- Rebrand from "Dreadnode Warpgate Templates" to "Ares Warpgate Templates" and update all references to Ares and new repository links
- Revise overview and template descriptions to clarify agent roles and architecture (red/blue team, CLI, orchestrator, GPU, AMI)
- Update and expand template matrix tables to reflect new image types, platforms, and roles, removing old/obsolete templates and sections (Crucible, Ray, GOAD)
- Rewrite quick start, usage, and validation instructions for current Warpgate workflow, including new multi-arch, GPU, and AMI build examples
- Update directory structure and template configuration documentation for new layout and template design
- Clarify prerequisites, environment requirements (GITHUB_TOKEN, AWS creds), and runtime instructions for each major agent image
- Remove outdated sections and simplify documentation to focus on Ares agents, containers, and AMIs
- Replace links, badges, and support information to align with the current Ares and Warpgate ecosystem
@l50 l50 force-pushed the fix/update-warpgate-readme branch from 1378e21 to 26dd7cc Compare April 23, 2026 23:50
@l50 l50 merged commit 9157164 into main Apr 24, 2026
13 checks passed
@l50 l50 deleted the fix/update-warpgate-readme branch April 24, 2026 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/templates Changes made to warpgate template configurations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant