For general information on Apollo, go to http://genomearchitect.org/.
Complete Apollo installation and configuration instructions are available from the Apollo documentation pages
Setup guide for deploying on production and custom configuration guide.
Launchable public Amazon EC2 images may also be found in most regions under the name 'Apollo' as well as instructions for docker.
The quick-start guide for developers shows how to easily get started with Apollo.
Migrating data from older versions
You can follow steps in our migration guide to move annotations and data from older versions.
Note about data directories
Apollo 2.0 allows you to add multiple data directories to your webapp, and it expects the data directories to be stored outside of the tomcat webapps directory. Use the WA2.0 quick-start guide to learn how to add new data directories for your organisms.
Important Note: All data from a webapps directory will disappear when doing tomcat "undeploy" operations, even if it is a symlink..
Launch Apollo in a temporary server
To launch Apollo with temporary settings, use the
apollo run-local command, which will initialize your server
automatically with an H2 (zero-configuration) database.
apollo run-local 8080
It will also use your custom settings if an apollo-config.groovy file has been setup.
Generate a war file
Users can generate a war file (for example target/apollo-1.0.2.war) that will be copied into their tomcat webapps directory for production deployments:
Note: make sure to create an apollo-config.groovy file following the sample data (e.g. sample-postgres-apollo-config.groovy) to make sure you use your preferred database settings.
Run locally for GWT development
Thanks to YourKit for providing us the use of their YourKit Java Profiler. YourKit supports Open Source.