Changing Documentroot for subscription

[Spikerok]

I have been trying variety of things, not sure on how to achieve this.
I have also followed this guide: https://gist.github.com/masum-sg/9786279#file-changing-default-document-root-in-plesk-html-L5 ; without much luck

I have main domain and clone domains. I want clone domains to use document root of main domain.

/var/www/vhosts/main.com/httpdocs is root dir for main.com and i want clone sites to use same dir.

I am using standards Centos 7 server.

 

[UFHH01]

Hi Spikerok,

as you don't provide enough informations about your operating system and your Plesk version ( incl. MU ) and left out as well informations, about your "clone domains" ( are these subdomains, alias domains ... ), I can only suggest to read the Plesk documentation for it:

For Plesk 12.5:

Working with a Staging Site ( online documentation: Reseller's Guide, Plesk 12.5 )

Adding Subdomains ( online documentation: Reseller's Guide, Plesk 12.5 )

Adding Domain Aliases ( online documentation: Reseller's Guide, Plesk 12.5 )​

 

[Spikerok]

I run Plesk 12.0.18 Update #70 on CentOS Linux 7.1.1503 (Core).

I have created two subscriptions:
- Subscription 1 called main.com and document root is /var/www/vhosts/main.com/httpdocs
- Subscription 2 called clone.com and document root is /var/www/vhosts/clone.com/httpdocs

I want Subscription 2 have document root at /var/www/vhosts/main.com/httpdocs

 

[Bitpalast]

I doubt that this can be done with Plesk, because each subscription can only be modified on the /[domain].[tld] level, but not on a higher level.

However you could do a workaround: On the linux console (login with SSH, use super user mode), remove the /httpdocs directory. Instead, create a symbolic link within the second subscription to the httpdocs of the first subscription, e.g. "ln -s /var/www/vhosts/main.com/httpdocs /var/www/vhosts/clone.com/httpdocs". The webserver will then serve all files from the other subscription.

There is a big problem with what you want to achieve, though: The access properties of the file system. As different subscriptions are owned by different users, you may run into severe issues in the subscription linked to the other, because that user will not be allowed to write to files owned by the other subscription's user. So basically this solution is bad in general. You should better use the standard way of adding domains within the same subscription. There you can easily set the "Hosting options" of your second domain to the same directory as you have set them for the first domain (normally "httpdocs").