Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
DEPRECATED. Content on this page will be updated and incorporated in other pages.
Each server environment is composed of an application server and database server.
Development supports the following activities:
This is an integration point between development and staging. Staging has a mirror of the production data with code from the development server. Staging is the place to finalize testing before new code lands on production.
Running the current stable release of VIVO. No new code can hit production without having gone through both development and staging.
UF has a sparql endpoint at sparql.vivo.ufl.edu. This sparql endpoint is open to the world and anyone may send queries to the server.
Since this server is open to the world, data is replicated from production to the sparql server database via MySQL master/slave replication.
The tools server is to help manage all of the other servers. This server is used to host the following activities:
Server Name | Description |
|
vivo.ufl.edu | Production apllication server | |
vivo.dbprod1.vivo.ufl.edu | Production database server | |
sparql.vivo.ufl.edu | Sparql Endpoint | |
tools.vivo.ufl.edu | Tools server | |
vivostagingweb.vivo.ufl.edu | Staging application server | |
vivostagingdb.vivo.ufl.edu | Staging database server | |
vivodevweb.vivo.ufl.edu | Dev application server | |
vivodevdb.vivo.ufl.edu | Dev database server |