Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.

The following assumes a development environment already exists, setup with all of the prerequisites (ant, tomcat, mysql, java, etc...). In addition, an SVN client installed locally with shell access to run commands from the command line is required.

Note to Windows users: The following paths are arbitrary Unix syntax, used only as a matter of familiarity and consistency.

1. Create a new directory on your machine where you will checkout the vitro and vivo projects from the svn server

mkdir -p ~/src/vivodev

2. Change to that directory and checkout both project trunks

3. Change into the newly created vivo directory and copy, creating a new file in the same location named


4. Open and make the appropriate changes using the install documentation as a guide. See installation guide. If you have deployed the release packaged vivo, then this is pretty much identical to what you're already familiar. The one gotcha that trips a lot of first timers up is that when working with the prepared release, no change is necessary for the vitro.dir property, but when working with our code checked out from SVN you need to set this value. If you've stuck to my recommended structure (checking out the vitro and vivo projects side-by-side) the following value should work (otherwise adjust accordingly):


5. Once you have in good shape, save your changes. It's also a good time to ensure that your mysql db and user (with necessary permissions) have been created and that your luceneIndex and uploads directories exist.

6. Deploy vivo (make sure you're in ~/src/vivodev)

ant all

7. Tail Tomcat's catalina log

tail -f /usr/local/tomcat/logs/catalina.out

8. In a separate terminal window, start Tomcat


9. Once the "server startup in XXXX ms" is displayed in the log, you should be able to load vivo in your browser.

See also

VIVO in Eclipse

1 Comment

  1. The VIVO source is tracked on git now, can we delete or archive this page? If and still exist they aren't publicly available.