Files

T

litiantian03 561b263c8b feat: add Bundle Skills, WeCom channel, configurable archive limit, fix #123

- Bundle Skills: attach skills to config bundles, auto-resolve on creation. Migration 022 adds openclaw_config_bundle_skills table. Fix #123
- WeCom channel: wecom connector with botId/secret/dmPolicy/allowFrom
- CLAWMANAGER_WORKSPACE_ARCHIVE_MAX_MIB controls archive size limit, synced to nginx client_max_body_size via start.sh
- Update deployment manifests, i18n, and frontend UI

2026-05-26 17:17:07 +08:00

2.7 KiB

Raw Permalink Blame History

Deployment Guide

ClawManager is packaged as a Kubernetes-first platform. This guide is the operational entry point for deploying the control plane, locating the relevant manifests in the repository, and understanding which services are expected to come up in a working environment.

Deployment Paths

Choose the deployment path that matches your environment:

Standard Kubernetes: deployments/k8s/clawmanager.yaml
K3s or lightweight clusters: deployments/k3s/clawmanager.yaml
End-to-end first-use walkthrough: User Guide

What Gets Deployed

ClawManager frontend and backend
MySQL for application state
MinIO for object storage-backed features
skill-scanner for skill analysis workflows
Kubernetes Services used for portal, gateway, and supporting traffic paths

Repository Entry Points

Kubernetes manifest: deployments/k8s/clawmanager.yaml
K3s manifest: deployments/k3s/clawmanager.yaml
Container startup script: deployments/container/start.sh
Nginx config: deployments/nginx/nginx.conf

Deployment Workflow

Choose the deployment path: standard Kubernetes or K3s/lightweight.
Prepare the cluster, storage strategy, and image source strategy for that environment.
Review the bundled manifest and adjust secrets, images, storage classes, and ingress exposure for your environment.
Deploy the platform components into the cluster.
Wait for the core services to become ready.
Validate frontend access, AI Gateway management pages, Security Center connectivity, and runtime creation flows.

Operational Notes

ClawManager is designed around in-cluster services and platform-mediated access rather than direct pod exposure.
Resource Management features depend on object storage and skill-scanner being available.
Runtime workspace .openclaw and .hermes archive import/export size is controlled by CLAWMANAGER_WORKSPACE_ARCHIVE_MAX_MIB. The default is 500 MiB; set the env var on the ClawManager app deployment when a larger or smaller limit is needed.
Production environments should review images, credentials, TLS, persistence, and networking policies before rollout.

2.7 KiB Raw Permalink Blame History