Currently in the provision_apache.module implements the verify task as follows:
function provision_apache_provision_verify() {
$exists = _provision_create_dir(PROVISION_VHOST_PATH, t("Virtual host configuration"), 0700);
_provision_apache_restart_apache(TRUE);
}
Since verify is used if the user edits a site, and - for instance - adds an alias, I suggest a call to
function _provision_apache_create_vhost_config($url, $data, $template = NULL)
would help...
Comments
Comment #1
adrian commentedThe code for this already exists basically, as the migrate/deploy commands.
deploy takes a site backup tarball, and rolls it out to a new url, making sure to go into the database and alter the files table to point to the new file system locations.
migrate creates a backup, then calls the deploy command on the target platform, if that succeeds it deletes it's own copy of the site.
Rename is essentially exactly the same as migrate, but only acts on the same platform.
and furthermore, clone is exactly the same as migrate/rename commands, but without the cleanup afterwards.
Comment #2
anarcat commentedComment #3
anarcat commentedcomment removed, see http://drupal.org/node/275737#comment-1968674
Comment #4
anarcat commentedComment #5
Anonymous (not verified) commentedAs far as I'm concerned, this is all complete per #275737: Rename sites (provision/backend) now. Marking fixed