Follow the house shell conventions

Constants UPPER_SNAKE, mutable locals PascalCase, braced expansions
throughout, per Development/Coding conventions in the vault.
This commit is contained in:
fisher
2026-08-23 08:57:15 +00:00
parent 952de1ea8e
commit fc40facfc5
6 changed files with 131 additions and 108 deletions
+17
View File
@@ -15,3 +15,20 @@ update may re-add it; if it's still done, just delete it again.)
- Publishing public releases to a separate GitHub repo → `ai-context/infrastructure/gitea-to-github-release.md`
- Uploading build artifacts to Cloudflare R2 from CI → `ai-context/services/cloudflare-r2.md`
- CI success/failure notifications via ntfy → `ai-context/services/ntfy.md`
## This project
- **What this repo is, how it is installed, troubleshooting** → `docs/OPERATIONS.md`
- **Non-obvious gotchas in this codebase** (health endpoint, `eval` pitfall,
importing `cd-target`) → `docs/hints.md`
- **Design, targets, networking, deployment status** → MCP vault,
`Home IT/Services/CD webhook (fleet deployment).md`
- **Why this exists, how to add a project, testing without a host** → MCP vault,
`Development/CD webhook development.md`
- **What a correct domaindingo deploy is** — this repo automates it, that note
defines it → MCP vault, `Development/DomainDingo Development.md`
- **Shell style for this repo** (constants `UPPER_SNAKE`, locals `PascalCase`,
braced expansions) → MCP vault, `Development/Coding conventions.md`
Before adding a deploy script to any application repository: don't. Add a target
to `targets.json` here instead.