#253: installation: co-existence of several Invenio sites on the same box
----------------------------+-----------------------------------------------
 Reporter:  simko           |       Owner:     
     Type:  enhancement     |      Status:  new
 Priority:  minor           |   Milestone:     
Component:  *installation*  |     Version:     
 Keywords:                  |  
----------------------------+-----------------------------------------------
 0) Sometimes it is interesting to install more than one Invenio
 instance on the same physical box.  When the instances are lightly
 used and their codebase does not change often, e.g. for demo purposes,
 then a simple technique is use another module name such as `ithaca`
 instead of `invenio` when installing the second instance, like this:

 {{{
 $ cd /usr/local/src
 $ tar xvfz cds-invenio-0.92.0.tar.gz
 $ mv cds-invenio-0.92.0 ithaca-0.92.0
 $ cd ithaca-0.92.0
 $ find . -type f -exec perl -pi -e 's,invenio,ithaca,g' {} \;
 $ mv po/cds-invenio.pot po/ithaca.pot
 $ configure --prefix=/opt/ithaca --with-weburl=ithaca.polito.it [...]
 }}}

 see:
 [[http://cdsware.cern.ch/lists/project-cdsware-
 users/archive/msg00686.shtml]]

 1) Some Invenio sites use such a technique and expressed interest in
 having this more automated inside the Invenio codebase itself.  The
 purpose of this task would be then to introduce a new configuration
 parameter such as:

 {{{
 $ ./configure --instancename=ithaca
 }}}

 that would perform the above steps behind the scenes, ideally altering
 installation files only, keeping codebase the same.

 2) An alternative to this simplistic technique is to set up
 PYTHONPATH properly for the two instances, e.g. see Ferran's
 approach:
 [[https://groups.cern.ch/group/project-cdsware-
 users/Lists/Archive/DispForm.aspx?ID=549]]

-- 
Ticket URL: <http://invenio-software.org/ticket/253>
Invenio <http://invenio-software.org>

Reply via email to