Openclaw Deploy

Build and deploy OpenClaw as Docker images or portable packages. Package OpenClaw with or without personal configuration for easy deployment to other servers.

Security Scan

The skill mostly does what its name says (build and package OpenClaw), but there are several inconsistencies and risky behaviors (copying user configs that can contain tokens, developer-hardcoded paths, and a buggy export script) that you should review before using it on real systems.

Purpose & Capability

The skill's stated purpose (build/package/deploy OpenClaw) aligns with the included scripts which copy the application and config directories and create tarballs. However there are developer-specific hardcoded paths (e.g., /home/zfanmy/...) and references in documentation to including 'DreamMoon 配置' and gateway/channel tokens — these are expected for a migration/backup tool but should be explicit to users because sensitive tokens may be packaged.

Instruction Scope

Runtime scripts read and copy the user's OpenClaw installation and configuration directories (OPENCLAW_INSTALL_DIR, OPENCLAW_CONFIG_DIR, defaulting to user home paths). That means private credentials or tokens stored in the config could be packaged and transferred. The SKILL.md and scripts also reference deploy.sh and export/deploy.sh behavior; some expected files (deploy.sh) are not present in the repository but export-portable.sh attempts to create one — that creation contains a malformed redirection which will likely break and produce unexpected output/errors.

Install Mechanism

This is instruction-only with embedded scripts (no install spec, no downloads). Nothing is fetched from external URLs during installation; scripts run locally. From an install mechanism perspective this is low risk, but running the scripts will perform filesystem operations so they should be inspected before execution.

Credentials

The skill declares no required credentials, but the scripts will copy the entire OpenClaw install directory and (optionally) the user's config directory into output packages. Those config files can contain API keys, gateway tokens, channel tokens, and other secrets (README even mentions 飞书、网关 token). Requesting no env vars but acting on user config is proportionate for migration, but it is a sensitive action that should be signposted and optional; the current scripts default to including full config for the 'full' package.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or global agent settings. It will create local directories and output tarballs when run, and some scripts create/expect directories under a developer path (/home/zfanmy), which is awkward but not a privilege escalation.

What to consider before installing

This skill appears to be a legitimate packaging/deployment tool, but review and test before using on real data. Specific recommendations: - Inspect the scripts (build-portable.sh, export-portable.sh, start.sh) yourself; do not run them until reviewed. - Be aware: the 'full' package copies your OpenClaw config directory (~/.openclaw by default). That directory frequently contains API keys, gateway tokens, and other secrets — sanitize or back up separately if you don't want those included. - The export script contains a broken heredoc/redirection that may fail to create the expected deploy.sh/README files; test in a disposable environment first. - The start scripts use developer-specific hardcoded paths (/home/zfanmy/...), which may create unexpected directories on your host; adjust those paths before running. - Prefer to run these scripts in an isolated VM/container or with copies of your install/config to verify behavior. - If you intend to deploy remotely, review any deploy scripts for scp/ssh behavior and ensure they won't leak packages to untrusted hosts. If you need help auditing specific files or sanitizing configs, provide which files/paths you plan to package and I can point out what to remove.

SKILL.md 元数据格式示例

---

name: openclaw-deploy description: Build and deploy OpenClaw as Docker images or portable packages author: zfanmy-梦月儿 version: 1.0.1 homepage: license: MIT keywords:

• openclaw
• deploy
• docker
• portable
• backup
• migration requires: bins:
  • node
  • npm
  • tar

---

OpenClaw Deploy

Build and deploy OpenClaw as Docker images or portable packages.

Features

• 🐳 Build Docker images (clean/full versions)
• 📦 Create portable packages for deployment
• 🚀 Deploy to remote servers with one command
• 💾 Backup and restore configurations

Quick Start

Build Portable Packages

# Build both clean and full versions
./scripts/build-portable.sh

# Export for deployment
./scripts/export-portable.sh

Deploy to Remote Server

# Deploy clean version
./export/deploy.sh user@remote-server clean /opt/openclaw

# Deploy full version
./export/deploy.sh user@remote-server full /opt/openclaw

Directory Structure

openclaw-deploy/
├── portable/clean/          # Clean version (no personal data)
├── portable/full/           # Full version (with config)
├── export/                  # Deployment packages
│   ├── openclaw-clean-portable.tar.gz
│   ├── openclaw-full-portable.tar.gz
│   └── deploy.sh
└── scripts/
    ├── build-portable.sh
    ├── export-portable.sh
    └── deploy.sh

Usage on Target Server

# Install Node.js
./install-node.sh

# Start OpenClaw
cd clean && ./start.sh   # or cd full && ./start.sh

# Access WebUI
open http://localhost:18789

Requirements

• Node.js 22.x
• Docker (optional, for Docker builds)
• curl, rsync (for deployment)

Configuration

Environment Variables

You can customize paths using environment variables:

# OpenClaw installation directory (default: auto-detect)
export OPENCLAW_INSTALL_DIR=/path/to/openclaw

# OpenClaw config directory (default: ~/.openclaw)
export OPENCLAW_CONFIG_DIR=/path/to/.openclaw

# Output directory (default: ./openclaw-portable-output)
export OUTPUT_DIR=/path/to/output

Example with Custom Paths

export OPENCLAW_INSTALL_DIR=/opt/openclaw
export OPENCLAW_CONFIG_DIR=/opt/config/.openclaw
export OUTPUT_DIR=/tmp/openclaw-packages

./scripts/build-portable.sh

Changelog

v1.0.1

• Fixed hardcoded paths
• Added environment variable support
• Improved error handling and dependency checks
• Added path validation

v1.0.0

• Initial release

Author

zfanmy-梦月儿