Manage Site Configuration
The Site Config section allows you to manage site-specific configuration settings for your Frappe Cloud site. These settings act as environment variables and control features that apply only to the selected site without affecting other sites on the same server.
Using Site Config, you can customize various behaviors of your site, such as email settings, caching, search functionality, and supported framework features.
Common Site Configuration Options
You can use Site Config to configure settings such as:
- Configure an email account for sending outgoing emails.
- Enable or disable website caching.
- Disable Global Search.
- Enable supported server-side features.
- Manage other site-specific configuration values.
Update Site Configuration
- Open your Frappe Cloud dashboard.
- Select the site you want to configure.
- Navigate to the Site Config tab.
- Enter or modify the required configuration values.
- Click Update Configuration to save the changes.
Frequently Asked Questions
Why can’t I enable Developer Mode?
Developer Mode is intentionally disabled on Frappe Cloud because it is designed for creating standard framework objects such as DocTypes, Reports, Pages, Workspaces, Print Formats, and other development artifacts. These objects are stored as JSON files inside an application.
Since the standard Frappe and ERPNext applications cannot be modified directly on Frappe Cloud, any custom development must be created within your own custom app.
Applications deployed on Frappe Cloud are ephemeral. Every time a new bench is deployed, the platform pulls a fresh copy of your application’s source code from its Git repository. Any changes made directly on the server would be overwritten during deployment.
To create custom DocTypes, Reports, Workspaces, or other framework components, first develop them inside a custom app, push the app to your Git repository, and then deploy the updated app on Frappe Cloud.
Keep all customizations inside a custom application instead of modifying the framework directly. This ensures your changes remain version-controlled, portable, and persist across deployments and updates.
