Deploy Moltbot To Fly

**Quick judgment** High-quality, Fly.io-focused deployment skill for Moltbot/Clawdbot that gives a complete, reproducible path from zero to a secure, persistent gateway with web UI access. Best suited to users comfortable with the CLI and basic server administration. **What it does well** - Provides a concrete `fly.toml` tuned for Moltbot (persistent volume, `CLAWDBOT_STATE_DIR=/data`, `--bind lan`, 2GB RAM, modern `[http_service]` usage). - Uses Fly secrets correctly for Anthropic/OpenAI API keys and the gateway token, keeping credentials out of source and config files. - Enforces security by requiring a shared gateway token *and* device pairing for UI access. - Walks through manual creation of `/data/moltbot.json` with consistent token-based auth setup. - Includes extensive troubleshooting guidance for token mismatches, DNS issues, config syntax, gateway binding, and corrupted state. **Key risks / limitations** - **Security depends on token hygiene**: If the gateway token is weak, reused, or leaked (e.g., pasted in logs, screenshots, or shared URLs), the gateway could be exposed. Users must treat it like a password. - **Manual SSH and JSON editing**: Several steps require logging into the Fly machine and editing JSON or running Node one-liners; mistakes here can cause config errors or broken pairing. - **Operational expertise expected**: Assumes familiarity with Fly CLI, DNS troubleshooting, and reading logs. Non-technical users may struggle despite the clear instructions. - **Resource assumptions**: Recommends 2GB RAM; users that downsize may hit OOM or instability, and the guide does not cover auto-scaling or multi-region setups. **Recommended scenarios** - You want a **self-hosted Moltbot gateway on Fly.io** with persistent state and are comfortable using the terminal. - You need a **secure, token-protected web UI** for AI agents and are willing to manage device pairing yourself. - You’re a developer or power user looking for a **clear, prescriptive deployment recipe** rather than a generic Fly.io or Docker guide. **Not ideal if** - You need a one-click, no-CLI deployment experience. - You’re unfamiliar with basic DevOps tasks (SSH, editing config files, handling secrets). - You require advanced production features out of the box (autoscaling strategies, observability beyond Fly logs, multi-tenant access control policies).