Fair enough – it’s not hard to persuade me not to do extra work!

 

It’s probably not worth adding a message to the post-install screen.  The install-fest at the Summit already suggested that people glaze over that information, so adding more there seems likely only to reduce the chances of people reading any of it.  Hopefully the internal links in the wiki to the configuration/customization page will make the information accessible to those who really want it…  and, of course, I’m always open to improving the wiki navigation/organization if there are ideas on making it clearer.

 

- Demian

 

From: Chanel Wheeler [mailto:Chanel.Wheeler@yavapai.us]
Sent: Thursday, November 08, 2012 10:41 AM
To: Demian Katz; vufind-general@lists.sourceforge.net
Subject: RE: Correctly setting DocumentRoot for VuFind 2

 

I didn’t enter / for the base path when I originally  ran the install script. Once I got the new DocumentRoot set up then I went back and changed the base path to / and restarted Apache. The CSS/JS files still wouldn’t load. It was removing /vufind2 from the AliasMatch lines that ultimately did the trick (in combination with RewriteBase / and removing the Alias line).

 

Personally I would be disinclined from suggesting that the installer should try to set this scenario up. When you’re first installing, all you really want (I think) is to get something out of the box that functions. Thus the simplest, most direct way to that is best. Then when you want to do funky things later, it’s supremely nice if there’s documentation to help you get there with the least effort. (But it wouldn’t hurt to include the link to the VuFind DocRoot documentation in the install.php report success text for those that just want it to get it over and done with.)

 

chanel

 

Chanel Wheeler

Library Network Programmer/Analyst

Yavapai Library Network

1120 Commerce Dr.

Prescott, AZ  86305

 

Phone: (928) 442-5741

chanel.wheeler@yavapai.us

Open a help desk ticket

 

From: Demian Katz [mailto:demian.katz@villanova.edu]
Sent: Thursday, November 08, 2012 6:31 AM
To: Chanel Wheeler; vufind-general@lists.sourceforge.net
Subject: RE: Correctly setting DocumentRoot for VuFind 2

 

Thanks for helping with the documentation!  One question: did you try just entering “/” as the base path when you ran the install.php script?  That should automatically take care of most of the httpd-vufind.conf configuration (though it won’t currently remove the Alias line).  Perhaps it would make sense to slightly extend the installer to do more of this configuration for you.  If you think it’s worthwhile, feel free to open a JIRA ticket so we don’t forget about it.  In the meantime, having this wiki page to point people to is a big help.

 

- Demian

 

From: Chanel Wheeler [mailto:Chanel.Wheeler@yavapai.us]
Sent: Wednesday, November 07, 2012 4:23 PM
To: Demian Katz; vufind-general@lists.sourceforge.net
Subject: RE: Correctly setting DocumentRoot for VuFind 2

 

Bingo. I’ll add it to the VuFind 2 wiki.

 

chanel

 

Chanel Wheeler

Library Network Programmer/Analyst

Yavapai Library Network

1120 Commerce Dr.

Prescott, AZ  86305

 

Phone: (928) 442-5741

chanel.wheeler@yavapai.us

Open a help desk ticket

 

From: Demian Katz [mailto:demian.katz@villanova.edu]
Sent: Wednesday, November 07, 2012 1:42 PM
To: Chanel Wheeler; vufind-general@lists.sourceforge.net
Subject: RE: Correctly setting DocumentRoot for VuFind 2

 

The CSS and JS files are loaded through the theme directories – they don’t live under public.  This is the appropriate block of the Apache configuration:

 

AliasMatch ^/vufind/themes/([0-9a-zA-Z-_]*)/css/(.*)$ /usr/local/vufind/themes/$1/css/$2

AliasMatch ^/vufind/themes/([0-9a-zA-Z-_]*)/images/(.*)$ /usr/local/vufind/themes/$1/images/$2

AliasMatch ^/vufind/themes/([0-9a-zA-Z-_]*)/js/(.*)$ /usr/local/vufind/themes/$1/js/$2

<Directory ~ "^/usr/local/vufind/themes/([0-9a-zA-Z-_]*)/(css|images|js)/">

  Order allow,deny

  allow from all

  AllowOverride All

</Directory>

 

Can you simply remove the “/vufind” part of the regular expression in the AliasMatch directives to fix the problem?

 

(I admit that I don’t think I’ve ever tried this, so maybe there is something more subtle at work).

 

- Demian

 

From: Chanel Wheeler [mailto:Chanel.Wheeler@yavapai.us]
Sent: Wednesday, November 07, 2012 1:41 PM
To: vufind-general@lists.sourceforge.net
Subject: [VuFind-General] Correctly setting DocumentRoot for VuFind 2

 

Hi,

 

I’ve just installed VuFind 2 off of Master. Has anyone successfully set up Apache so that the VuFind URL doesn’t have to contain “/vufind2”? Using the same method as I did for VuFind 1.x (with edits based on 2.0 structure) isn’t working. In particular, if I get vufindtest.yln.info to serve up the page, it can’t get to the CSS and JS files because they’re absolutely referenced from /usr/local/vufind2 (not /usr/local/vufind2/public).

 

Any ideas?

 

Thanks,

chanel

 

Chanel Wheeler

Library Network Programmer/Analyst

Yavapai Library Network

1120 Commerce Dr.

Prescott, AZ  86305

 

Phone: (928) 442-5741

chanel.wheeler@yavapai.us

Open a help desk ticket