An aside to AmaZili Communication comment · January 14, 2019 1:18 PM
The previous note Says that resource sharing is not possible - but that isn't true because I do it ...
... Its not directly supported by Plesk - you have to use RDP and access the server file system directly
create your shared resources as a folder somewhere suitable on your server - (not in any particular subscription/domain) but where you can get access to it via plesk file manager
use plesk file manager to ensure the correct access rights are in place for each of the domains that are to access it
in each domain use the windows CMD line tool MKLINK to create a junction - this creates a virtual directory where you presently have your unshared resources with the same name as before and hence has the same folder name as before
now you have one instance of your master resource with as many domains using it as you wish
but think access rights access rights access rights while you are doing this
but think concurrency of access and file sharing implications.
its good any easy for readonly stuff - like software and static web pages. Take your life in your hands with anything else
.. and by default anyone in a client domain tries to ftp to the linked folder will not actually be able to change the files
An aside to AmaZili Communication comment · January 14, 2019 1:18 PM
The previous note Says that resource sharing is not possible - but that isn't true because I do it ...
... Its not directly supported by Plesk - you have to use RDP and access the server file system directly
create your shared resources as a folder somewhere suitable on your server - (not in any particular subscription/domain) but where you can get access to it via plesk file manager
use plesk file manager to ensure the correct access rights are in place for each of the domains that are to access it
in each domain use the windows CMD line tool MKLINK to create a junction - this creates a virtual directory where you presently have your unshared resources with the same name as before and hence has the same folder name as before
now you have one instance of your master resource with as many domains using it as you wish
but think access rights access rights access rights while you are doing this
but think concurrency of access and file sharing implications.
its good any easy for readonly stuff - like software and static web pages. Take your life in your hands with anything else
.. and by default anyone in a client domain tries to ftp to the linked folder will not actually be able to change the files