← Back to PRs

#20698: docs: add production VPS deployment guide

by aiagentswiz open 2026-02-19 07:09 View on GitHub →
docs size: XS
## Summary Adds a practical guide for running OpenClaw 24/7 on a VPS, covering: - systemd service configuration - Remote access via Tailscale - Cron watchdog for scheduler reliability - Disk and memory monitoring - Backup strategy - Security hardening checklist - Troubleshooting common issues - Tips from production experience ## Context Based on real-world experience running OpenClaw daily on a Hetzner VPS with Discord, Telegram, voice calls, cron pipelines, and custom skills. The existing docs cover installation but there was no guide for hardened production deployment. ## AI Disclosure - [x] AI-assisted (drafted with Claude, reviewed and validated against real production setup) - [x] Fully tested — all recommendations are from a live production environment - [x] I understand what the content covers Happy to iterate on feedback! <!-- greptile_comment --> <h3>Greptile Summary</h3> Added a production VPS deployment guide covering systemd setup, remote access, monitoring, and security hardening. The guide provides practical advice based on real production experience. Key issues found: - Incorrect systemd command (`gateway start --foreground` should be `gateway run`) - Security contradiction (systemd runs as root but checklist advises against it) - Missing Mintlify frontmatter required for docs - Minor issues with Tailscale URL format and documentation consistency The content is valuable and fills a documentation gap, but needs corrections to the systemd service configuration and frontmatter before merging. <h3>Confidence Score: 2/5</h3> - This PR introduces documentation with critical command syntax errors that would cause systemd service failures - Score reflects critical issues: the systemd ExecStart command uses `gateway start --foreground` which is incorrect (should be `gateway run`), and there's a logical conflict between running as root in the service file while advising against it in the security checklist. These errors would cause the systemd service to fail or violate security best practices. The missing Mintlify frontmatter also breaks documentation standards. While the content is valuable, these issues must be fixed before merge. - docs/vps-production.md requires attention - fix the systemd command syntax, resolve the root user contradiction, and add required frontmatter <sub>Last reviewed commit: fa5f16f</sub> <!-- greptile_other_comments_section --> <sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</sub> <!-- /greptile_comment -->

Most Similar PRs