Once site A has been cloned to site B, we should be able to repeatedly clone site A over site B. For this, we need #699920: site relationships first. But once that is done, the "existence" check should be overriden if there's a clone relationship between the two sites. I'm not sure we should make it both ways, ie. that cloned sites can overwrite masters, but let's start with a unidirectional A -> B override for now.

Comments

adrian’s picture

adrian commented

You can now clone sites over each other in the backend.

we just need a way to schedule these tasks on the UI>

Anonymous’s picture

Anonymous (not verified) commented
Project: Hosting » Hostmaster (Aegir)
Version: 6.x-0.4-alpha3 » 6.x-2.x-dev

I'd like to see this in 2.x

To quote from a more recent ticket #1356704: Allow overwriting when cloning a site:

Adding a check box for overwriting would be helpful on scenarios where you want to re-clone a site with the latest improvements. Currently, the alternative is to backup, disable, delete, and then clone the site. In essence, it would run the following commands:

# File re-clone.sh
# Usage: sh re-clone [origin-site] [destination-site] [destination-platform]
drush @$2 provision-backup
drush @$2 provision-disable
drush @$2 provision-delete
drush @$1 provision-clone '$2' '$3'
drush @$2 cc all
ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Version: 6.x-2.x-dev » 7.x-3.x-dev

This can be accomplished in DevShop with 'sync' tasks. But something like this in core won't make it into Aegir 2.

helmo’s picture

helmo commented

There is #2027673: Integrate Provision Sync/Hosting Sync modules into DevShop .. which seems to be working pretty nice.

helmo’s picture

helmo commented
Issue summary: View changes
Status: Active » Closed (won't fix)