Problem
`kingofalldata.com` is hardcoded in the gestate command:
- GPG email: `$ENTITY@kingofalldata.com` (commands/gestate/command.sh)
- Likely other places in entity templates, .env defaults, etc.
This prevents operators who fork koad:io for their own domain from getting correct identities. An operator running their kingdom at `alice.example.com` would gestate entities with email `alice@kingofalldata.com`.
Fix
Introduce a global `KOAD_IO_DOMAIN` config variable — set in `~/.koad-io/.env` and readable by all commands.
Default: `kingofalldata.com` (backwards compatible).
Operator sets it once:
```bash
~/.koad-io/.env
KOAD_IO_DOMAIN=example.com
```
Then gestate uses:
```bash
GPG_EMAIL="${ENTITY}@${KOAD_IO_DOMAIN:-kingofalldata.com}"
```
Scope
- `commands/gestate/command.sh` — GPG email
- Any other places in the framework that hardcode `kingofalldata.com`
- Document the variable in `~/.koad-io/.env.example` (or equivalent)
Filed by
Vulcan — noticed while building gestate GPG key generation (#58)
Problem
`kingofalldata.com` is hardcoded in the gestate command:
This prevents operators who fork koad:io for their own domain from getting correct identities. An operator running their kingdom at `alice.example.com` would gestate entities with email `alice@kingofalldata.com`.
Fix
Introduce a global `KOAD_IO_DOMAIN` config variable — set in `~/.koad-io/.env` and readable by all commands.
Default: `kingofalldata.com` (backwards compatible).
Operator sets it once:
```bash
~/.koad-io/.env
KOAD_IO_DOMAIN=example.com
```
Then gestate uses:
```bash
GPG_EMAIL="${ENTITY}@${KOAD_IO_DOMAIN:-kingofalldata.com}"
```
Scope
Filed by
Vulcan — noticed while building gestate GPG key generation (#58)