#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:
Resolution: | Keywords:
-----------------------------+----------------------------------------------
Comment (by rchyla):
The 2) link is not accessible (access denied)
Another alternative is to have all 'changeable' values in the config and
have invenio read them at runtime. This is different from the current
situation, because if system is 'really portable' one can change few lines
in the config, move the installation into a different folder, adapt apache
config, and voila!
I generally miss the purpose of make/make install in the CMS system like
Invenio -- it just makes things very complex and everything what make does
can be done much more easier with python alone or by changing requirements
(for instance, bin/* files have shebang which makes it tied to the
configured python interpreter, where there could be just one entry point
that simply executes the other bin applications, there is more of those,
generally, if any file is there hardcoded in the source, it makes it non-
portable). The make mechanism basically allows Invenio to do away with the
current situation and not being forced to restructure files a bit more.
--
Ticket URL: <http://invenio-software.org/ticket/253#comment:1>
Invenio <http://invenio-software.org>
