Difference between revisions of "WebApollo Embed"
From GMOD
(→How it works) |
(→How it works) |
||
Line 13: | Line 13: | ||
==How it works== | ==How it works== | ||
The key thing that must be done for multiple species/users/sessions on one server is creating multiple tomcat webapps by cloning the WebApollo Directory tree. | The key thing that must be done for multiple species/users/sessions on one server is creating multiple tomcat webapps by cloning the WebApollo Directory tree. | ||
+ | |||
+ | [[File:demo_user.png]] | ||
+ | [[File:ref_seqs.png]] | ||
+ | [[File:ref_seqs_in_db.png]] |
Revision as of 16:30, 8 October 2013
Contents
Description of setting up WebApollo as an embedded web application
Use case
- Run WebApollo as an integrated component of a web application
- Support multiple species
- Support multiple users with private editing session
- Users can have multiple projects/species
- Jump straight to edit mode without user login
Installation
- Use the regular installation/configuration procedure
- Use exemplar species sequence annotations, we will add multiple species support below
How it works
The key thing that must be done for multiple species/users/sessions on one server is creating multiple tomcat webapps by cloning the WebApollo Directory tree.