Issue Title: Establish 'Zaviago Core' as Default Template for New Site Deployments
1. Issue Description
We have a customized version of Frappe, forked from the main upstream branch and tailored to our specific needs, named 'beta.zaviago.com'. The goal is to set this customized version as the standard template for all new site deployments. This means that every time a user creates a new site, it should automatically use the 'Zaviago Core (beta.zaviago.com)' repository for deployment.
2. Steps to Reproduce
Not applicable as this is a setup/configuration request.
3. Current Behavior
New site deployments currently use the dev.zaviago.com Frappe branch as their base template.
4. Expected Behavior
All new site deployments should default to using the 'Zaviago Beta' version of Frappe.
5. Goal
To standardize our site deployment process by using the customized 'Zaviago Core' Frappe fork as the default source for all new sites, ensuring consistency and integration of our specific modifications across deployments.
Issue Title: Establish 'Zaviago Core' as Default Template for New Site Deployments
1. Issue Description
We have a customized version of Frappe, forked from the main upstream branch and tailored to our specific needs, named 'beta.zaviago.com'. The goal is to set this customized version as the standard template for all new site deployments. This means that every time a user creates a new site, it should automatically use the 'Zaviago Core (beta.zaviago.com)' repository for deployment.
2. Steps to Reproduce
3. Current Behavior
4. Expected Behavior
5. Goal
To standardize our site deployment process by using the customized 'Zaviago Core' Frappe fork as the default source for all new sites, ensuring consistency and integration of our specific modifications across deployments.