The hosting description file can be written in the YAML or JSON format,
and contains the list of clients, subscriptions, addon domains,
mailboxes, etc. to be transferred from the source server. You can find
sample hosting description files here. This topic
describes how to configure a number of commonly used parameters to
ensure that the migration is successful.
Specifying the path to the web content data
To specify the path to the web content data, both on the source server
and the destination server, use the following parameters in the
subscriptions section:
-
source_webspace_root
- The absolute path to the directory
containing all files available to the customer on the source server.
Can be specified on the subscription level only (e.g.,
/home/vhosts/example.com
). -
source_document_root
- The absolute path to the directory
containing only the files served via HTTP. Can be specified on the
subscription, addon domain, or subdomain levels (e.g.,
/home/vhosts/example.com/httpdocs
). -
target_document_root
- The directory that will contain the files
served via HTTP on the destination server. The path is relative to
subscription’s root directory on the destination server. Can be
specified on the subscription, addon domain, or subdomain levels
(e.g.,data/www
. If the domain name is example.com, and the
virtual hosts directory in Plesk is/var/www/vhosts
, the absolute
path to the document root directory on the destination will be
/var/www/vhosts/example.com/data/www
). If left unspecified, the
Plesk default value will be used.
Note: If the configuration file does not contain the access information for
the source server, the source_webspace_root
and
source_document_root
paths will be treated as local on the
destination server.
If you need to prevent specific directories or files from being
migrated, use the exclude
directive with the
source_webspace_root
and source_…