The other thing I've now tried is to add the AllowSymLink in my apache httpd.conf file, but the current path remains the same in both slave and master.

I've been looking up some symlink documentation on forums to find out how to get my apache install working properly.

I'm pretty sure this is more apache's fault than jms.

Thanks for all the help, though. Much appreciated.


ross

It seems that AllowSymLink may not change the result.
I have seen that also for another customer and I don't know which parameters make this symbolic link not processed correctly.

Concerning the installation directory created with a symbolic link, you can delete it manually before deploying the "unzip".

This will create an exact copy of the installation directory.
I have not tried to use the "copy" action due to the directory dependencies.
I have prefered the unzip because I know the result.

Well, I tried changing the installation to the unzip in a template, then added a new site based on the template. Seemed to work, because the installation dir is now a directory, and not a sym link. Still same error.

I'm pretty sure it must be something going on with my apache installation or something. Sorry to keep on about this. Once I get this running, JMS will solve many of my headaches.

I'll keep on with some research into sym links.


ross

False alarm!

going to the slave site (based on the unzip option) and adding the /installation at the end got me to the install without errors. Went through the steps, made the new db prefix slave1_, and presto! Working!

Can't thank you enough, all that work and I finally got it! Send me a link to your feedback and I'll write a glowing review of the support offered.

Thanks again.


Ross

Thanks again for all your help! I now have multiple slaves up and running, just one last question, probably a silly one.

Since I want the multisites to usually have their own independant templates/mainmenu etc, I'll want to specify how the administrator folder works, yes? Much like how you suggested the istallation folder be a tar file, instead of a symlink.

Currently, the admin folder is set as a sym link. I know this means I'll need to administer each slave site individually, but trust me that this is what I want. Do I set it to unzip, or to copy?


ross

Ross,
It is always better to keep the Symbolic Links because this will simplify your maintenance in case of bug fixes or whatever.
If you unzip an administration directory that is effectivelly possible you will have to replicate yourself the update.
So the maintenance benefit of JMS will be lost because you will have to maintain this directory yourself.

The fact that will will unzip the administration directory will not change the fact that when a slave site will want to install an extension, it will still request that it is installed on the master website before.
The problem will be that you will not be able to use the JMS Tools facility for the extension as it assumes that the PHP code is already present for the extensions (that will not be the case if you create an indepedent administrator directory).

I know that some customers have used this unzip/copy facility and they manage thing themselves.

All I can tell you is to test yourself and discover the limits of such architecture.