agentenv-framework-protocol 0.1.469__tar.gz → 0.1.470__tar.gz

{agentenv_framework_protocol-0.1.469 → agentenv_framework_protocol-0.1.470}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: agentenv-framework-protocol
-Version: 0.1.469
+Version: 0.1.470
 Summary: Open data-plane protocol and server SDK for agent environments.
 Project-URL: Homepage, https://www.agentenvframework.com
 Project-URL: Documentation, https://www.agentenvframework.com/docs

{agentenv_framework_protocol-0.1.469 → agentenv_framework_protocol-0.1.470}/examples/website/notes/README.md

@@ -80,8 +80,11 @@ the container before using it.
 ## Register it
 
 In a bundle, `env.toml` declares the env: copied to a bundle's `envs/notes/`, `agent-env bundle register <bundle>`
-builds the image with that folder as its context. Its keys are `type`, `environment_name` and `backend_image`; domains
-are not one of them, as they come from the card. Without a bundle:
+builds the image with that folder as its context. Its keys are `type`, `environment_name` and `backend_image`, and it
+may name `domains`, the names the site is reached by, such as `domains = ["notes.example"]`. These win over the
+card's; without them a computer reaches the site by the names its card declares (`notes.test`), or as
+`notes.localhost` when it declares none. Two sites of one multi env can't claim one name. Without a bundle (`--domain`
+names the site, and can be repeated):
 
 ```bash
 agent-env env website put --id notes-site --server-dockerfile Dockerfile --server-docker-context .

{agentenv_framework_protocol-0.1.469 → agentenv_framework_protocol-0.1.470}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "agentenv-framework-protocol"
-version = "0.1.469"
+version = "0.1.470"
 description = "Open data-plane protocol and server SDK for agent environments."
 readme = "README.md"
 license = "Apache-2.0"