I have been trying to get my store online to use Shared SSL. I went ahead and purchased the hosting space, assuming that Catalog would generate the necessary scripts and pages for me to run on the SSL space, but it looks like I can only run it on one that has extra Actinic scripts. I am really peeved about this. No where in the documentation that came with Catalog or in the Advanced User guide can I find anything that says these extra scripts are necessary. It seems to me to be pretty essential information for what is supposed to be an out of the box solution to e-commerce.
So after further searching deep into Actinic's web site, I have come across the pdf file Split SSL Configuration: A Host's Guide. It seems I can set up Catalog to run across two servers as a normal SSL situation. So can anyone tell me what is "NFS access" that needs to be set up between the two computers.
Also I have to have the scripts checked before use on the SSL server, so I have to upload them manually using ftp. Does anyone know what scripts must be on the secure server, the guide above very helpfully only says "Additional modules (eg ACTINIC.pm, ActinicOrder.pm etc)" Does anyone know what the "etc" is?
Sorry to be bitter, but I do feel quite let down by this lack of information. Any help would be gratefully received.
Thanks,
Matthew
So after further searching deep into Actinic's web site, I have come across the pdf file Split SSL Configuration: A Host's Guide. It seems I can set up Catalog to run across two servers as a normal SSL situation. So can anyone tell me what is "NFS access" that needs to be set up between the two computers.
Also I have to have the scripts checked before use on the SSL server, so I have to upload them manually using ftp. Does anyone know what scripts must be on the secure server, the guide above very helpfully only says "Additional modules (eg ACTINIC.pm, ActinicOrder.pm etc)" Does anyone know what the "etc" is?
Sorry to be bitter, but I do feel quite let down by this lack of information. Any help would be gratefully received.
Thanks,
Matthew
Comment