@octelium/console-agent 0.1.0-b-ca02.1.1 → 0.1.0
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.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -29,13 +29,13 @@ octelium-console-agent ───────────── Cordium Workspace
|
|
|
29
29
|
|
|
30
30
|
## Running inside a Cordium Workspace
|
|
31
31
|
|
|
32
|
-
The enterprise `AgentService` (`octelium.api.main.enterprise.v1.AgentService`) provisions the agent of every User on demand: `InitializeAgent` creates the User's personal `octelium.<user>` Cordium Space, its `default` Template and a primary Workspace that serves the agent as its default Application on port `8080`. The Template installs Node.js upon the first start of a Workspace if the image lacks it (`ON_CREATE`) and starts `npx --yes --prefer-online @octelium/console-agent@<version> serve` on every start (`POST_START`). Development builds use their Git branch as the npm tag, falling back to `dev` when build branch metadata is absent. Production uses
|
|
32
|
+
The enterprise `AgentService` (`octelium.api.main.enterprise.v1.AgentService`) provisions the agent of every User on demand: `InitializeAgent` creates the User's personal `octelium.<user>` Cordium Space, its `default` Template and a primary Workspace that serves the agent as its default Application on port `8080`. The Template installs Node.js upon the first start of a Workspace if the image lacks it (`ON_CREATE`) and starts `npx --yes --prefer-online @octelium/console-agent@<version> serve` on every start (`POST_START`). Development builds use their Git branch as the npm tag, falling back to `dev` when build branch metadata is absent. Production always uses `latest`. The Template is generated from the `spec.agent` section of the enterprise ClusterConfig:
|
|
33
33
|
|
|
34
34
|
| Field | Description |
|
|
35
35
|
| --- | --- |
|
|
36
36
|
| `isDisabled` | Disables the `AgentService` |
|
|
37
37
|
| `llm.service`, `llm.model` | The default LLM Service and model (i.e. `llm.service` and `llm.model` below) |
|
|
38
|
-
| `version` | Development override for the `@octelium/console-agent` npm tag or version; production uses
|
|
38
|
+
| `version` | Development override for the `@octelium/console-agent` npm tag or version; production always uses `latest` |
|
|
39
39
|
| `image`, `limit` | The Workspace image and compute resources |
|
|
40
40
|
| `config` | Any additional configuration (same structure as `config.json`), passed via `OCTELIUM_CONSOLE_AGENT_CONFIG_JSON` |
|
|
41
41
|
|
|
@@ -61,7 +61,7 @@ spec:
|
|
|
61
61
|
|
|
62
62
|
`npx … doctor` checks the configuration, the Octelium API access and the LLM access.
|
|
63
63
|
|
|
64
|
-
`make build-apiserver` embeds the current Git branch
|
|
64
|
+
`make build-apiserver` embeds the current Git branch in the API server. The Cluster's usual development/production detection selects the agent tag; `OCTELIUM_DEV=true` forces development and `OCTELIUM_PRODUCTION=true` forces production. The npm tag must already be published. Branches outside `main`, `dev` and `b-*` can be published manually with their branch name as the npm tag, or use `spec.agent.version: dev` during development.
|
|
65
65
|
|
|
66
66
|
The `--prefer-online` flag checks for tag updates at every Workspace start. After changing the Cluster's agent configuration or upgrading from the fixed-version launcher, call `InitializeAgent` to reconcile its Template, then restart the Workspace to run the selected package version.
|
|
67
67
|
|
package/package.json
CHANGED