frappe-ops-bench

To configure multi-tenancy, map custom domains using common_site_config and site_config keys, regenerate nginx configurations, and verify routing behavior to ensure safe Frappe bench operations for multiple customer sites.

Safe Frappe bench updates require backing up before destructive actions, running bench update inside the bench directory, and executing migrate after code changes to prevent production failures from misconfigured environment assumptions.

Setting up a Frappe bench requires running bench init with a pinned branch, creating sites, configuring domain routing, and validating scheduler health to ensure production-grade operations and correct multi-tenancy behavior.

Frappe bench commands fail in production due to misconfigured environment assumptions, missing version pinning, incorrect site routing, or unsafe operational steps, requiring step-order guardrails and aligned configuration handling to prevent deployment failures.

Bench backup and restore in multi-tenant environments require backing up before destructive actions, validating scheduler health, and applying correct site_config patterns to prevent downtime surprises during database schema changes and site lifecycle management.

Pinning the Frappe branch before bench init and new-site commands is required to prevent misconfigured environments, ensuring safe operational steps, correct site routing, and proper app lifecycle management in production deployments.