forked from Selig/openclaw-skill
Selig
4c966a3ad2
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.
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
# Linux App
|
|
|
|
## Overview
|
|
|
|
OpenClaw's Gateway operates on Linux systems, with Node.js as the preferred runtime environment. Bun is not recommended for the Gateway (WhatsApp/Telegram bugs).
|
|
|
|
## Quick Start for VPS Users
|
|
|
|
The beginner pathway involves four primary steps:
|
|
|
|
1. Installing Node 22 or later
|
|
2. Installing the OpenClaw package globally via npm
|
|
3. Running the onboard command with daemon installation
|
|
4. Establishing an SSH tunnel to access the interface locally
|
|
|
|
## Installation Options
|
|
|
|
Multiple installation approaches are available:
|
|
|
|
- Standard setup procedures
|
|
- Experimental Bun support
|
|
- Nix package manager integration
|
|
- Containerized Docker deployment
|
|
|
|
## Service Management
|
|
|
|
OpenClaw implements systemd user services by default, though system-wide services suit shared or persistent server environments. The installation process offers three command variations for establishing the Gateway service, along with diagnostic and repair capabilities through the doctor command.
|
|
|
|
### Gateway service install options
|
|
|
|
- `openclaw onboard --install-daemon`
|
|
- `openclaw gateway install`
|
|
- `openclaw configure` (select Gateway service when prompted)
|
|
|
|
Use `openclaw doctor` to diagnose or repair installations.
|
|
|
|
## Configuration
|
|
|
|
A minimal systemd service unit requires specifying the Gateway startup command with port configuration, restart policies, and user-level enablement through systemctl commands.
|