As long as you do not change the location of the Koha files on the file system, you would not need to change the Koha configuration files. If you are using the koha-httpd.conf file as an included file then you would need to adjust the virtual directories, but that is the very thing you are proposing for wherever you have your virtual directories specified. So, go ahead and change the virtual directories. You should have no problem from doing that. Thomas D Quoting Robert Flach <webmaster@allauthors.com> :
---------------- Beginning of the original message ------------------
I'd like to install Koha 2.2.4 on a server where it will be integrated into an existing website. For various reasons I need to limit web activity to the default port 80. This means I need to have both the opac and the intranet sites run on port 80. My intention is to differentiate them using just directories under a single virtualserver instance. It looks like this should be possible based on what is being done in the httpd.conf. Just move the appropriate lines into directory .htaccess files under the already existing web path. My question is will this cause any problems with the backend/scripts/utilities/etc. If so, can anyone point me in the direction to get started modifying things? If not, I'll probably end up eventually modifying the installer.pl script on my server to accomodate this type of setup. Is this something that I should pass back to the Koha developer group if I do so? Thanks very much, Robert _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
------------------- End of the original message ---------------------
--------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com