VIVO Documentation
...
Download the distribution from the VIVO repository on GitHub. The standard distribution consists of the projects required to create a home directory for VIVO, and to copy the web application and search index. All the compiled code and dependencies are resolved from the Maven central repository at the time you run Maven.
...
Code Block | ||
---|---|---|
| ||
vivo-1.12.02/ pom.xml example-settings.xml home/ pom.xml src webapp/ pom.xml src |
...
In order to install the development code from GitHub, you need to clone both the Vitro and VIVO repositories from the vivo-project organization. These clones should be in sibling directories called called "Vitro" and "VIVO" respectively. These will all point to the 1.12.3-SNAPSHOT:
Code Block | ||
---|---|---|
| ||
$ git clone https://github.com/vivo-project/Vitro.git Vitro -b rel-1.12.0-RC2-maint $ git clone https://github.com/vivo-project/VIVO.git VIVO -b rel-1.12.2-maint $ git clone https://github.com/vivo-project/VIVO.git VIVO -b rel-1.12.0-RC $ ls -l-project/Vitro-languages.git Vitro-languages -b rel-1.12.2-maint $ git clone https://github.com/vivo-project/VIVO-languages.git VIVO-languages -b rel-1.12.2-maint drwxr-xr-x user group 1 Dec 12:00 Vitro drwxr-xr-x user group 1 Dec 12:00 VIVO drwxr-xr-x user group 1 Dec 12:00 Vitro-languages drwxr-xr-x user group 1 Dec 12:00 VIVO-languages |
Note |
---|
If you do not place the Vitro code in a sibling directory called "Vitro", then you will have to supply the "vitro-core" property to Maven - e.g. mvn package -Dvitro-core=~/Vitro It is expected that the Maven project numbers are kept in sync between the Vitro / VIVO projects, however, depending on when you update / sync your repositories, you may need to adjust the project version numbers for the build to work. |
...
This file needs to be created following the Maven Settings Reference. A template file already exists in the "installer" directory within the VIVO project, called "example-settings.xml". You may copy this file (it can be called anything you like) , and edit the contents to fit your requirements / system configuration.
...
The end result should be a directory structure such as:
No Format |
---|
${SOLR_HOME}/server/solr/vivocore/core.properties └── conf/ ├── currency.xml ├── elevate.xml └── ... |
Start Solr
No Format |
---|
${SOLR_HOME}/bin/solr start |
When solr was started it created the managed-schema automatically from the schema.xml and is no longer needed
Update VIVO runtime.properties as below to point to the URL of your Solr
No Format |
---|
vitro.local.solr.url = http://localhost:8983/solr/vivocore |
...
VIVO is a multithreaded web application that may require more threads than are permitted under the default configuration of your operating system. Ensure that your installation can support the required number of threads for your application. For a Linux production environment, you may wish to make the following edits to /etc/security/limits.conf, replacing apache and tomcat with the appropriate user or group name for your your setup:
apache hard nproc 400 tomcat hard nproc 1500 |
...
Tomcat allows you to override these context fragments by adding Context elements to to server.xml. If If you decide to do this, be sure that your new Context element includes the necessary deployment parameters from the overridden context fragment.
...
If you have completed the previous steps, you have good indications that the installation was successful.
...
...