Record the MCP server deployment decisions in the spec #36
@@ -35,10 +35,11 @@ same string across all of those: the VM, the container, the Caddy host, the Matr
|
||||
account, and the Bitwarden machine account for a given agent all share one name, so
|
||||
that grepping the infrastructure for `nisse-ops` finds everything.
|
||||
|
||||
**Sites** are identified by their domain stem: `garrett-hall` (Arlington) and
|
||||
`hartman-hut` (Cross Plains). As with agent names, one string is used everywhere a site
|
||||
appears. For an MCP server instance (F3), that means its container name, its
|
||||
Vaultwarden machine account, and its MCP tool prefix.
|
||||
**Sites** are identified by their domain stem: `garrett-hall` (Arlington, hosts under
|
||||
|
dongar marked this conversation as resolved
Outdated
|
||||
`garrett-hall.com`) and `hartman-hut` (Cross Plains, hosts under `hartman-hut.com`).
|
||||
As with agent names, one string is used everywhere a site appears. For an MCP server
|
||||
instance (F3), that means its container name, its Vaultwarden machine account, and
|
||||
its MCP tool prefix.
|
||||
|
||||
The three artifacts live as three packages in **one repository, `nisse`** (decision
|
||||
recorded in Part H). Directory and package names carry the identity. If mirrored to
|
||||
|
||||
Reference in new issue
Block a user
One note (and I think this was wrong in the original prompt), the domains for the two sites end in garrett-hall.com, and hartman-hut.com.
Good catch. The identifiers themselves stay the same:
garrett-hallandhartman-hutare the stems ofgarrett-hall.comandhartman-hut.com. But the text said "domain stem" without naming the domains, so a reader could not check which domain it meant. Each site now names its domain: "hosts undergarrett-hall.com" and "hosts underhartman-hut.com".