Hi,

In case anyone has this same issue, I thought I would provide the solution. Thanks go to Abda Anne for a helpful example!

Here are the steps I took:

1) in invenio-local.conf, set CFG_SITE_URL to http://our.server/docs (and CFG_SITE_SECURE_URL accordingly)

2) Add the following to httpd.conf:

AddDefaultCharset UTF-8
ServerSignature Off
ServerTokens Prod
WSGIRestrictStdout Off
<Files *.pyc>
   deny from all
</Files>
<Files *~>
   deny from all
</Files>

3) In the default (non-ssl) virtual host, add the <Directory /opt/invenio/var/www> tag, DirectoryIndex line, Alias lines, WSGI lines and <Directory /opt/invenio/var/www-wsgi> tag from the auto-generated "invenio" file.

4) Change the Alias lines to have a prefix of /docs (Alias /img/ to Alias /docs/img/)

5) Change WSGIScriptAlias / ... to WSGIScriptAlias /docs ... (not /docs/ !)

6) Do the same for the SSL virtual host using the invenio-ssl file.

- Corey


On 07/07/2012 11:20 AM, Corey Reed wrote:
Hi,

I would like to use Invenio for our experiment, and to have it run on
our existing web server. The web server uses apache2. I would like
Invenio to show up at "http://our.server/docs/";.

I tried simply placing "Alias /docs/ /opt/invenio/var/www/" in our
default virtual host, and then copying all the <Directory> and WSGI
lines from Invenio's automatically generated apache site file.

This causes apache to properly serve files from these directories,
however the Invenio (test) site does not function -- I'm assuming
because the WSGI daemon won't serve files properly?

I was wondering if anyone has done this or has some information about
how to set it up?

Thanks very much!

- Corey


PS - I could get the non-ssl part of Invenio to work as I wanted by
setting up a reverse proxy from /docs/ to a virtual host on port 8082,
but this can't work because the login goes via ssl, and I don't want to
change that port away from 443, so I can't use the same solution for
ssl. This makes me wonder if there's a way to use a reverse proxy
pointing to localhost that will work.

Reply via email to