$npx -y skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloudUse when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure. Prevents failed deployments from misconfigured cloud settings and API misuse. Covers Frappe Cloud dashboard, Press API, site provisioning, bench management, envi
| 1 | # Frappe Cloud & Press |
| 2 | |
| 3 | Complete reference for Frappe Cloud managed hosting and Press self-hosted alternative. |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## Quick Reference: Frappe Cloud Concepts |
| 8 | |
| 9 | | Concept | Description | |
| 10 | |---------|-------------| |
| 11 | | **Site** | A single Frappe instance with its own database, domain, and apps | |
| 12 | | **Bench** | A shared runtime environment hosting one or more sites with the same app versions | |
| 13 | | **Server** | The underlying infrastructure (VM) running one or more benches | |
| 14 | | **Private Bench** | A dedicated bench for a single customer with full control | |
| 15 | | **Shared Bench** | A Frappe-managed bench shared across multiple sites | |
| 16 | | **Press** | The open-source platform (AGPL-3.0) that powers Frappe Cloud | |
| 17 | | **Agent** | Flask application on each server enabling Press-to-site communication | |
| 18 | |
| 19 | --- |
| 20 | |
| 21 | ## Decision Tree: Frappe Cloud vs Self-Hosted |
| 22 | |
| 23 | ``` |
| 24 | Choosing hosting strategy: |
| 25 | ├── Small team, want zero ops overhead? |
| 26 | │ └── Frappe Cloud (Shared Bench) — fastest time to production |
| 27 | ├── Need custom server configuration? |
| 28 | │ ├── Budget for managed infra? → Frappe Cloud (Private Bench) |
| 29 | │ └── Want full control? → Self-hosted with bench |
| 30 | ├── Need to host Frappe for multiple clients? |
| 31 | │ ├── Want managed platform? → Frappe Cloud |
| 32 | │ └── Want own platform? → Self-hosted Press |
| 33 | ├── Regulatory/compliance — data must stay on-premises? |
| 34 | │ └── Self-hosted (bench or Press) |
| 35 | └── Development/testing environment? |
| 36 | ├── Quick prototype → Frappe Cloud (free trial) |
| 37 | └── Long-term dev → Local bench installation |
| 38 | ``` |
| 39 | |
| 40 | --- |
| 41 | |
| 42 | ## Frappe Cloud Overview |
| 43 | |
| 44 | Frappe Cloud is a fully managed hosting platform for the Frappe stack. It handles server provisioning, backups, updates, monitoring, and scaling. |
| 45 | |
| 46 | ### Core Features |
| 47 | |
| 48 | | Feature | Details | |
| 49 | |---------|---------| |
| 50 | | **Automated backups** | Scheduled daily backups with retention policies | |
| 51 | | **Automatic updates** | Managed update cycles for Frappe apps | |
| 52 | | **Scaling** | Horizontal and vertical scaling without downtime | |
| 53 | | **Multi-tenancy** | Multiple independent sites per bench | |
| 54 | | **SSL/TLS** | Automatic certificate provisioning and renewal | |
| 55 | | **Monitoring** | Real-time server and site monitoring | |
| 56 | | **Role-based access** | Granular permissions for team members | |
| 57 | | **Billing** | Daily/monthly subscriptions, wallet credits, multiple payment methods | |
| 58 | |
| 59 | ### Infrastructure Options |
| 60 | |
| 61 | | Option | Use Case | |
| 62 | |--------|----------| |
| 63 | | **Shared Bench** | Cost-effective for small sites; Frappe manages the bench | |
| 64 | | **Private Bench** | Dedicated environment; custom app versions and update schedules | |
| 65 | | **Dedicated Server** | Full server for high-traffic or compliance requirements | |
| 66 | |
| 67 | --- |
| 68 | |
| 69 | ## Frappe Cloud Dashboard |
| 70 | |
| 71 | ### Site Management |
| 72 | |
| 73 | The dashboard provides centralized control for all site operations: |
| 74 | |
| 75 | - **Create sites** — Provision new sites on shared or private benches |
| 76 | - **Install/remove apps** — Add or remove Frappe apps from sites |
| 77 | - **Backups** — Manual and scheduled backups, restore from backup |
| 78 | - **Domain management** — Add custom domains with automatic SSL |
| 79 | - **Site config** — Edit `site_config.json` via the dashboard |
| 80 | - **Monitoring** — View CPU, memory, disk usage, and request logs |
| 81 | - **Site actions** — Migrate, update, suspend, archive, or transfer sites |
| 82 | |
| 83 | ### Bench Management |
| 84 | |
| 85 | - **Create benches** — Set up shared or private benches |
| 86 | - **App management** — Select apps and their versions/branches |
| 87 | - **Update scheduling** — Control when benches receive updates |
| 88 | - **Environment variables** — Set custom environment variables |
| 89 | - **SSH access** — Connect to bench via SSH for debugging |
| 90 | - **Log browser** — View application and error logs |
| 91 | - **Database access** — Query the database via the dashboard |
| 92 | |
| 93 | ### Server Management |
| 94 | |
| 95 | - **Provision servers** — Create servers across multiple cloud providers |
| 96 | - **Scale resources** — Upgrade CPU, memory, and storage |
| 97 | - **Storage add-ons** — Attach additional storage volumes |
| 98 | - **Server snapshots** — Create and restore server snapshots |
| 99 | |
| 100 | --- |
| 101 | |
| 102 | ## Deploying Apps on Frappe Cloud |
| 103 | |
| 104 | ### Adding a Custom App |
| 105 | |
| 106 | 1. Navigate to **Apps** in the Frappe Cloud dashboard |
| 107 | 2. Click **Add App** and provide the GitHub repository URL |
| 108 | 3. Select the branch to deploy |
| 109 | 4. Configure build settings if needed |
| 110 | 5. The app becomes available for installation on sites within compatible benches |
| 111 | |
| 112 | ### App Marketplace |
| 113 | |
| 114 | Frappe Cloud includes a marketplace w |