fisher/my-cd-webhook
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Point the README at the vault notes

Browse Source
This commit is contained in:
fisher
2026-08-23 08:57:31 +00:00
parent fc40facfc5
commit 777a2d321f
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+14
View File
@@ -160,6 +160,20 @@ Fields: `name`, `enabled`, `repo`, `branch`, `env`, `host`, `stack_dir`,
`CD_TARGETS_FILE` points the tooling at a scratch manifest for testing. It `CD_TARGETS_FILE` points the tooling at a scratch manifest for testing. It
changes which manifest is read, never which host this machine may act as. changes which manifest is read, never which host this machine may act as.
## Documentation
This README covers the design. The rest lives where the fleet's other
documentation does:
| Where | What |
|---|---|
| `docs/OPERATIONS.md` | runbook — install, deploy by hand, roll back, rotate a secret, troubleshoot |
| `docs/hints.md` | non-obvious gotchas in this codebase |
| `docs/active-context.md` | routing index; read it before opening the rest |
| Vault: `Home IT/Services/CD webhook (fleet deployment)` | operational view — targets, networking, status |
| Vault: `Development/CD webhook development` | why it exists, how to add a project |
| Vault: `Development/DomainDingo Development` | what a correct domaindingo deploy is; this repo automates it |
## Not yet done ## Not yet done
- **Port `21600` is proposed, not allocated.** The Port registry's rule is to - **Port `21600` is proposed, not allocated.** The Port registry's rule is to