docs: fix stale Getting Started environment docs #83
No reviewers
Labels
No labels
automation
automerge
ci
infra
migrated/beads
priority/P2
refactoring
repo-maintenance
status/in-progress
testing
type/epic
type/task
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
Personal/cluster!83
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/fix-getting-started"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The README documented a staging environment that does not exist, showed
manifests/{env}/apps/ where the generated path is apps-{env}/, and did not
explain that bootstrap is a one-time per-environment step.
the real dev/infra/prod environments.
automated prune + selfHeal, not tracked in Git) and the Argo CD prerequisite.
Closes #80
The README documented a staging environment that does not exist, showed manifests/{env}/apps/ where the generated path is apps-{env}/, and did not explain that bootstrap is a one-time per-environment step. - Replace staging examples with a clearly marked your-env placeholder and list the real dev/infra/prod environments. - Document the rendered bootstrap object (Application apps-{env} in argocd, automated prune + selfHeal, not tracked in Git) and the Argo CD prerequisite. - Correct the repository-structure diagram to apps-{env}/ plus per-app dirs. - Mention just diff {env}, clone URL, and just switch running git add. Refs #80fd77a95f19f777bb6dcd