Rename Installation to Instance
Follows the portal: the noun is "instance" everywhere the app says it — UI strings, CLI output, error details, docs and comments. The wire keys (`instance_id`, `instance_token`) and the hub route this calls move with it. An existing cloud.json is adopted rather than refused: without the key alias the dataclass fails to parse, which the caller swallows and reads as "never enrolled" instead of "reconnect". `instance_key` on a node type becomes `target_key`. It means the outside thing a node points at, which is a different sense of the word, and keeping both would put two meanings of "instance" in one codebase. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015YrQnKV3bnQd4K342y8tKj
This commit is contained in:
@@ -33,7 +33,7 @@ help: ## Show available targets
|
||||
|
||||
# Hostname the local stack is served under. Never .env's DOMAIN: a checkout
|
||||
# configured for a deployment carries that deployment's domain, and a local
|
||||
# stack started under it answers to the same names the live installation does.
|
||||
# stack started under it answers to the same names the live instance does.
|
||||
# Target-specific on purpose — an exported DOMAIN outranks --env-file in
|
||||
# compose interpolation, which would put the *production* targets on localhost.
|
||||
# `make dev DOMAIN=fluksio.com` still wins.
|
||||
|
||||
Reference in New Issue
Block a user