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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

These instructions are for how to backup your VIVO installation, and what to backup.

There are three components that you will want to backup

  1. The VIVO directory. This would include the VIVO code installed, images, uploads, etc...
  2. The VIVO relational database
  3. The VIVO RDF store

Step-by-step guide

 

Things to think about

  1. If you've made changes to code, e.g. changes to freemarker template files, etc... then you might want to consider branching the VIVO and Vitro github repositories. This would act as a "backup" of any changes that you've made and backups would be handled by, say, github.  There is a vivo project template on Github that is an example of this approach.  It uses Git submodules to track the VIVO and Vitro code and keeps local modifications in the local git repository.  A VIVO site could clone this repository and have a blank instance to get stared with and have the benefit of any local changes being in a git repository.  A working example of this is the Brown VIVO modifications.   

 

  • No labels

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