Commit activity
Last 12 weeks · 0 commits
Community health
1 of 6 standards met
28
✓README○License○Contributing○Code of Conduct○Issue Template○PR Template
Recent fixes
Summary VPS deployment infrastructure: Docker Compose, GitHub Actions CI/CD via SSH, Cloudflare Tunnel, systemd service, automated backups Migration from Fly.io: Removed fly.toml and old workflow, transformed all documentation to VPS context Security hardening (14 vulnerabilities closed): Non-root container, pinned Bun, loopback-only bind, SSH known hosts, no-new-privileges, AES256-encrypted backups, sandbox/discovery/logging/tools/plugins security defaults, Bonjour disabled, OS hardening docs (fail2ban, unattended-upgrades) New GitHub Secrets required Test plan [ ] Verify Docker image builds successfully () [ ] Confirm container runs as non-root ( → ) [ ] Confirm gateway binds to loopback only [ ] Verify is active via [ ] Confirm Cloudflare Tunnel connects from inside the container [ ] Test encrypted backup produces files [ ] Verify deploy workflow validates secret [ ] Confirm includes sandbox, discovery, logging, tools, plugins security fields Summary by CodeRabbit Release Notes New Features VPS-based deployment with Docker and Cloudflare Tunnel integration Automated encrypted backup capability for data persistence Enhanced security configuration with non-root runtime and resource limits Chores** Migrated deployment infrastructure from Fly.io to self-hosted VPS Updated deployment documentation and operational guides Added comprehensive architecture documentation
I am using gemini for my brain and was getting this error The docs appear to be using a GEMINI_API_KEY if using an env var. https://docs.openclaw.ai/concepts/model-providers#google-gemini-api-key Summary by CodeRabbit Configuration Updated the required API key environment variable from GOOGLE_API_KEY to GEMINI_API_KEY for Gemini provider integration. Documentation Updated guides and documentation to reference GEMINI_API_KEY for all Gemini setup and authentication procedures. Chores** Updated deployment workflow configuration to align with the new API key variable naming.
I'm getting confused by the steps. Also setting it up on the couch from my phone on a family ski trip 😂 The way my head wants it to work is 1. Set up GitHub secrets 2. Deploy But it looks like I need to 1. Spin up a fly instance 2. Set up the CF tunnel 3. GitHub secrets 4. Deploy I'm not sure what the right steps are but hopefully we can update the operations md to help ppl after me 😎
Structured data for AI agents
Repository: kentcdodds/flying-jarvis. Description: Clawdbot running on fly.io Stars: 91, Forks: 9. Primary language: JavaScript. Languages: JavaScript (76.1%), Shell (12.9%), Dockerfile (11.1%). Open PRs: 0, open issues: 0. Last activity: 6mo ago. Community health: 28%. Top contributors: kentcdodds, Copilot, basicBrogrammer.