This configuration is deprecated.
The configuration wizard allows painlessly
for very versatile configuration organisation
without the trouble of manually tuning file lxr.conf.
See the
multiple databases configuration
page.
You can use a single database for several projects,
provided your source trees respect the following constraints:
- the version names are different between trees;
The search engine indexes are thus specific to a tree
- the filenames are different between trees.
The references in the database unambiguously point
to the correct file
If any of the above conditions is violated
(which happens nearly systematically
as soon as the project is no longer a very small one),
you may still display your source trees,
but the hyperlinks will probably be buggy.
You might be better off with the
multiple databases configuration.
Put the database and search engine parameters in the global section.
, 'dbname' => db_designation
, 'dbuser' => lxr_db_user
, 'dbpass' => lxr_db_password
, 'search_enginedir' => directory
where 'search_enginedir' is either
'glimpsedir' or 'swishdir'.
Eventually, you may keep the 'search_enginedir'
in the tree-specific parameter group to maintain separate indexes
for the search engine.
Or, better, define 'search_enginedirbase'
in the global section,
which implicitly creates independent indexes.
