Files

Selig 4c966a3ad2 Initial commit: OpenClaw Skill Collection

6 custom skills (assign-task, dispatch-webhook, daily-briefing,
task-capture, qmd-brain, tts-voice) with technical documentation.
Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.

2026-03-13 10:58:30 +08:00

1.5 KiB

Raw Blame History

OpenClaw on GCP Compute Engine

Overview

This guide establishes a persistent OpenClaw Gateway on Google Cloud's Compute Engine using Docker, designed for reliable 24/7 operation at approximately $5-12 monthly.

Key Setup Steps

The deployment process involves:

GCP Project Configuration - Create a project and enable the Compute Engine API
VM Provisioning - Deploy a Debian 12 instance (e2-small recommended with 2 vCPU, 2GB RAM)
Docker Installation - Set up containerization on the host system
Repository Cloning - Obtain the OpenClaw codebase
Persistent Directories - Create ~/.openclaw and workspace folders for state preservation
Environment Configuration - Define .env with tokens and credentials
Binary Baking - Embed required tools (gog, goplaces, wacli) in the Docker image at build time
Container Launch - Start the gateway service

Critical Architecture Decision

Installing binaries inside a running container is a trap. Anything installed at runtime will be lost on restart. All external dependencies must be embedded during image construction via the Dockerfile.

Access Method

The guide recommends SSH port forwarding rather than direct exposure: keep the Gateway loopback-only on the VM; access via SSH tunnel.

State Persistence

Long-lived data (configurations, tokens, workspace artifacts) survives container restarts through host volume mounts, while the container itself remains ephemeral and rebuilable.

1.5 KiB Raw Blame History