PyPI - cyclo-manager - Versions diffs - 0.4.0.dev0__tar.gz → 1.0.0.dev0__tar.gz - Mend

cyclo-manager 0.4.0.dev0tar.gz → 1.0.0.dev0tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (20) hide show

{cyclo_manager-0.4.0.dev0 → cyclo_manager-1.0.0.dev0}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cyclo-manager
-Version: 0.4.0.dev0
+Version: 1.0.0.dev0
 Summary: cyclo_manager CLI: pip-installable launcher for cyclo_manager server and UI containers. Run 'cyclo_manager up' to start Docker stack.
 License-Expression: Apache-2.0
 Requires-Python: >=3.10
@@ -160,7 +160,7 @@ The API reads it as `CONFIG_FILE=/app/config.yml` inside the container.
 | Key | Description |
 |-----|-------------|
-| **`robot_container`** | Primary robot Docker container name (e.g. `ai_worker`). Used by the UI System page and service bringup. Must be a key in `sockets` and cannot be `host_agent`. |
+| **`supported_robot_containers`** | Robot Docker container names that can open the System page (e.g. `ai_worker`, `open_manipulator`). Each must be a key in `sockets` and cannot be `host_agent`. |
 | **`sockets`** | Map of logical name → agent **Unix socket path as seen inside the API container** (under `/agents/...`). Include robot/service containers and `host_agent`. |
 s6 **service names** are not listed in config; each in-container agent reports them at runtime.
@@ -168,20 +168,17 @@ s6 **service names** are not listed in config; each in-container agent reports t
 ### Example (bundled default)
 ```yaml
-robot_container: ai_worker
+supported_robot_containers:
+  - ai_worker
+  - open_manipulator
 sockets:
   ai_worker: "/agents/ai_worker/s6_agent.sock"
+  open_manipulator: "/agents/open_manipulator/s6_agent.sock"
   cyclo_intelligence: "/agents/cyclo_intelligence/s6_agent.sock"
   host_agent: "/agents/host/host_agent.sock"
 ```
-### Validation (API startup)
-- At least one socket entry besides `host_agent`
-- `robot_container` must exist in `sockets`
-- All socket paths must be non-empty strings
 To use a different config layout, mounts, or local source builds, use the repository’s **`docker-compose.dev.yml`** — see [Custom config and development](#custom-config-and-development).
 ---

{cyclo_manager-0.4.0.dev0 → cyclo_manager-1.0.0.dev0}/README.md RENAMED Viewed

@@ -146,7 +146,7 @@ The API reads it as `CONFIG_FILE=/app/config.yml` inside the container.
 | Key | Description |
 |-----|-------------|
-| **`robot_container`** | Primary robot Docker container name (e.g. `ai_worker`). Used by the UI System page and service bringup. Must be a key in `sockets` and cannot be `host_agent`. |
+| **`supported_robot_containers`** | Robot Docker container names that can open the System page (e.g. `ai_worker`, `open_manipulator`). Each must be a key in `sockets` and cannot be `host_agent`. |
 | **`sockets`** | Map of logical name → agent **Unix socket path as seen inside the API container** (under `/agents/...`). Include robot/service containers and `host_agent`. |
 s6 **service names** are not listed in config; each in-container agent reports them at runtime.
@@ -154,20 +154,17 @@ s6 **service names** are not listed in config; each in-container agent reports t
 ### Example (bundled default)
 ```yaml
-robot_container: ai_worker
+supported_robot_containers:
+  - ai_worker
+  - open_manipulator
 sockets:
   ai_worker: "/agents/ai_worker/s6_agent.sock"
+  open_manipulator: "/agents/open_manipulator/s6_agent.sock"
   cyclo_intelligence: "/agents/cyclo_intelligence/s6_agent.sock"
   host_agent: "/agents/host/host_agent.sock"
 ```
-### Validation (API startup)
-- At least one socket entry besides `host_agent`
-- `robot_container` must exist in `sockets`
-- All socket paths must be non-empty strings
 To use a different config layout, mounts, or local source builds, use the repository’s **`docker-compose.dev.yml`** — see [Custom config and development](#custom-config-and-development).
 ---

{cyclo_manager-0.4.0.dev0 → cyclo_manager-1.0.0.dev0}/cyclo_manager.egg-info/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cyclo-manager
-Version: 0.4.0.dev0
+Version: 1.0.0.dev0
 Summary: cyclo_manager CLI: pip-installable launcher for cyclo_manager server and UI containers. Run 'cyclo_manager up' to start Docker stack.
 License-Expression: Apache-2.0
 Requires-Python: >=3.10
@@ -160,7 +160,7 @@ The API reads it as `CONFIG_FILE=/app/config.yml` inside the container.
 | Key | Description |
 |-----|-------------|
-| **`robot_container`** | Primary robot Docker container name (e.g. `ai_worker`). Used by the UI System page and service bringup. Must be a key in `sockets` and cannot be `host_agent`. |
+| **`supported_robot_containers`** | Robot Docker container names that can open the System page (e.g. `ai_worker`, `open_manipulator`). Each must be a key in `sockets` and cannot be `host_agent`. |
 | **`sockets`** | Map of logical name → agent **Unix socket path as seen inside the API container** (under `/agents/...`). Include robot/service containers and `host_agent`. |
 s6 **service names** are not listed in config; each in-container agent reports them at runtime.
@@ -168,20 +168,17 @@ s6 **service names** are not listed in config; each in-container agent reports t
 ### Example (bundled default)
 ```yaml
-robot_container: ai_worker
+supported_robot_containers:
+  - ai_worker
+  - open_manipulator
 sockets:
   ai_worker: "/agents/ai_worker/s6_agent.sock"
+  open_manipulator: "/agents/open_manipulator/s6_agent.sock"
   cyclo_intelligence: "/agents/cyclo_intelligence/s6_agent.sock"
   host_agent: "/agents/host/host_agent.sock"
 ```
-### Validation (API startup)
-- At least one socket entry besides `host_agent`
-- `robot_container` must exist in `sockets`
-- All socket paths must be non-empty strings
 To use a different config layout, mounts, or local source builds, use the repository’s **`docker-compose.dev.yml`** — see [Custom config and development](#custom-config-and-development).
 ---

{cyclo_manager-0.4.0.dev0 → cyclo_manager-1.0.0.dev0}/cyclo_manager_cli/config/config.yml RENAMED Viewed

@@ -1,8 +1,11 @@
 # cyclo_manager Configuration
-robot_container: ai_worker
+supported_robot_containers:
+  - ai_worker
+  - open_manipulator
 sockets:
   ai_worker: "/agents/ai_worker/s6_agent.sock"
+  open_manipulator: "/agents/open_manipulator/s6_agent.sock"
   cyclo_intelligence: "/agents/cyclo_intelligence/s6_agent.sock"
   host_agent: "/agents/host/host_agent.sock"

{cyclo_manager-0.4.0.dev0 → cyclo_manager-1.0.0.dev0}/pyproject.toml RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "cyclo-manager"
-version = "0.4.0.dev0"
+version = "1.0.0.dev0"
 description = "cyclo_manager CLI: pip-installable launcher for cyclo_manager server and UI containers. Run 'cyclo_manager up' to start Docker stack."
 readme = "README.md"
 license = "Apache-2.0"