[MRM-701] correct some missing information in the documentation for setting up a separated installation base

Submitted by: Martin Höller
Merged from: r639128


git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@639129 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Porter 2008-03-20 03:09:59 +00:00
parent 42a62ceef1
commit 9563940b42
1 changed files with 5 additions and 4 deletions

View File

@ -27,15 +27,16 @@ Installing Standalone Distribution of Apache Archiva
This is achieved by the following steps:
[[1]] Creating the base location. For example, you might install Archiva in <<</opt/archiva-1.0>>> and the data in <<</var/archiva>>>
[[1]] Creating the base location. For example, you might install Archiva in <<</opt/archiva-1.0>>> and the data in <<</var/archiva>>>. Create the directories <<</var/archiva/logs>>>, <<</var/archiva/data>>> and <<</var/archiva/conf>>>.
[[2]] Move the <<<conf>>> and <<<data>>> directories from the Archiva installation to the new location. If you've previously run Archiva, you may need to edit
<<<conf/archiva.xml>>> to change the location of the repositories
[[2]] Copy the configuration files from the Archiva installation (eg <<</opt/archiva-1.0/conf>>> to the new location (eg. <<</var/archiva/conf>>>). If you've previously run Archiva, you may need to edit <<<conf/archiva.xml>>> to change the location of the repositories
[[3]] Set the environment variable <<<PLEXUS_BASE>>> to the data location (in bash, be sure to export the variable).
[[3]] Set the environment variable <<<PLEXUS_BASE>>> to the data location (eg. <<</var/archiva>>>). In bash, be sure to export the variable.
[[4]] Start Archiva standalone as described above from the installation location
Note, that Archiva still needs write access to the installation directory, as the application server needs to extract the WAR and services.
* Configuring Archiva
Archiva's configuration is loaded from the following files, in order of most precedent: