ReferenceConfiguration

Configuration

Understand the workspace, permission, resource, and network concepts that shape a Jio deployment.

Jio configuration describes where tools operate and which actions they may perform. Keep policy explicit, reviewable, and close to the deployment it controls.

Illustrative schema

The keys below communicate policy concepts. Adapt them to the configuration interface and version used by your Jio build.

jio.yaml
# Illustrative policy shape — adapt keys to your Jio build.
workspace:
  host: workspace.example.com
  path: /srv/jio/projects/demo

permissions:
  read: true
  write: true
  execute: ask

resources:
  cpu: 2
  memory: 4Gi
  timeout: 15m

network:
  mode: restricted

Workspace concepts

ConceptPurposeGuidance
HostSelects the remote machine or serviceUse a stable internal identity, not an unverified address
PathDefines the filesystem boundaryResolve to one explicit absolute root
Workspace nameGives the bridge a stable targetKeep names unique within an operator scope
LifecycleControls persistenceMatch retention to the trust level of the task

Permission and limit concepts

ConceptTypical valuesGuidance
Readallow, denyUsually required; still constrain the root
Writeallow, ask, denyAsk or deny for sensitive workspaces
Executeallow, ask, denyPrefer approval until commands are well understood
CPU and memorynumeric limitsApply at the operating-system or runtime level
TimeoutdurationBound both commands and idle sessions
Networkdeny, restricted, allowStart restricted and document exceptions

Policy precedence

When local approval rules and remote enforcement differ, the stricter rule should win. The remote service must never assume that a local client has already authorized a request.

Validate changes

After editing policy, repeat four checks: an allowed read, an allowed write or command, a denied out-of-root operation, and a denied network or resource action. Record the effective configuration alongside the results.

On this page