Hi Chuck
I'll repeat these instructions complete with a little more detail to avoid misunderstanding.
This method allows you to have a client domain that has BOTH customer specific files AND shared files.
- Set up a master domain in Plesk to contain the library code. This makes it easier to upload new versions via FTP than if you put the code c:\library.
- Install the library code in a directory structure that includes the application name then version number. e.g. /library/app/v000. This allows new versions to be added without disturbing domains that are still using old versions.
- Set up client domains in Plesk as usual
- Log in locally or use Terminal Services (or similar) to start the IIS MMC. Find the client domain and create a virtual folder that points at the master domain's library folder. e.g. /library. Unfortunately this step cannot be done in Plesk.
- Run the app from the client domain e.g.
http://www.client.com/library/app/v000/default.asp
- You can even have local ASP code that includes library ASP code e.g. <!-- #INCLUDE VIRTUAL="/client.com_non_ssl/library/app/v000/inc/functions.asp" -->
This method makes a client domain that is identical to a master domain, but retains the client domain name in the browser address. This is also known as an 'Alias'. This feature is standard in the new Plesk 7.
- Set up a master domain in Plesk.
- Set up client domains in Plesk as usual
- Log in locally or use Terminal Services (or similar) to start the IIS MMC. Find the client domain and change its home folder to point at the master's home.
Cheers, Julian
www.inCharge.co.uk