Files
Yang Yang Xie 440260a0f6 Overhaul docs for auto-bootstrap, Local CA, and whoami tutorial
- Remove starter.json (no longer needed — gateway auto-bootstraps on first boot)
- Add envoy/envoy.yaml static bootstrap config
- Fix docker-compose.yml to use envoy.yaml instead of starter.json
- Update README: fix quick start flow, add Local CA section, add tutorial link
- Rewrite getting-started.md: auto-bootstrap, Local CA, bring-your-own-CA
- Update envoy-config.md: replace import section with auto-bootstrap explanation
- Add docs/tutorial-whoami-local-https.md: end-to-end local HTTPS with whoami
- Add configs/README.md: clarify configs dir purpose

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-20 17:16:06 -07:00
..

Example Configurations

This directory contains example Aegis database snapshots that can be imported via Gateway → Import.

Note

: On first boot, Aegis automatically seeds a working baseline configuration — an HTTP listener (port 10080), HTTPS listener (port 10443), and the acme-renewer cluster. You do not need to import any file to get started.

These snapshots are useful when you need a non-standard starting point or want to replicate a specific topology.

After importing

  1. Add your TLS certificates — Certificates → issue via ACME or Local CA
  2. Update filter chains — edit https_listener to add your domain's SNI match, cluster, and TLS secret
  3. Point clusters at your services — add clusters for each upstream service

Secrets are not included

TLS private keys are never exported or committed to source control. Add them via the Certificates page after importing.