If you can't set 2 environmental variables, then you can't run Koha at all. If your Apache processes run as your own user, you might be able to set the environmental variables in a profile. This seems unlikely though. You also might be able to use .htaccess, but do you know whether Bluehost actually supports .htaccess? and supports SetEnv in .htaccess? Really your host should tell you how to accomplish this: it's a very common configuration. --joe On Wed, Aug 13, 2008 at 11:16 AM, Dwayne Collins <dcollins@prcsa.ca> wrote:
Hi all,
Thanks for the information, Joe. I made the changes you suggested and things still weren't working for me. With a little further investigation, I've discovered another problem -- Bluehost does not allow me to make alterations to apache to make the linkages to koha's conf file.
Is there a way to use .htaccess to circumvent this?
I'm beginning to think I should stick to running koha off a server in the backroom...
Cheers, Dwayne
Joe Atzberger wrote:
I don't think you want to use their code. The version they gave you is an inefficient form that applies to all their users.
All you want to do is add /home/prcsaca/perl to the "SetEnv PERL5LIB..." lines in your .conf file.
So you might have something like: SetEnv PERL5LIB "/home/prcsaca/perl:/home/prcsaca/kohaclone"
--joe
On Tue, Aug 12, 2008 at 12:48 PM, Dwayne Collins <dcollins@prcsa.ca>wrote:
You will need to add /home/prcsaca/perl to the include path. You can do this by adding the following code to your script:
BEGIN { my $homedir = ( getpwuid($>) )[7]; my @user_include; foreach my $path (@INC) { if ( -d $homedir . '/perl' . $path ) { push @user_include, $homedir . '/perl' . $path; } } unshift @INC, @user_include; }