Difference between revisions of "Analytics"
From CoGepedia
m (→Configure Apache to Proxy the /analytics Endpoint) |
m (→Get Analytics Running:) |
||
| (19 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
CoGe Analytics is a metrics and analytics engine for the CoGe platform written on Clojure's web framework Noir. | CoGe Analytics is a metrics and analytics engine for the CoGe platform written on Clojure's web framework Noir. | ||
| − | |||
| − | |||
== How To: Deploy on a Server via Apache Webserver == | == How To: Deploy on a Server via Apache Webserver == | ||
| Line 18: | Line 15: | ||
*Leingingen - [https://github.com/technomancy/leiningen Leiningen - Automate Clojure projects without setting your hair on fire.] | *Leingingen - [https://github.com/technomancy/leiningen Leiningen - Automate Clojure projects without setting your hair on fire.] | ||
| − | + | === Configuring Analytics to the Database === | |
| + | |||
| + | Once you have all the prerequisites installed, you need to get the Greentea (Analytics) repo from Github. Run: | ||
| + | |||
| + | $ git clone https://github.com/LyonsLab/Greentea.git | ||
=== Get Analytics Running: === | === Get Analytics Running: === | ||
| − | + | Install [http://genomevolution.org/wiki/index.php/Teabag Teabag] to get Greentea running. | |
| − | + | ||
| − | + | '''---Alternatively---''' | |
| + | |||
Inside the cloned directory run: | Inside the cloned directory run: | ||
| − | + | ||
| − | + | $ lein run &> /dev/null & | |
| + | |||
| + | Leiningen should pull in all the required dependencies'''*''' and start a Jetty servlet running on port 3456. | ||
Check localhost:3456 to verify that the analytics platform is running. | Check localhost:3456 to verify that the analytics platform is running. | ||
| − | === Configure Apache to Proxy the /analytics Endpoint === | + | === Configure Apache to Proxy the Servlet Port to the /analytics Endpoint === |
| − | Now to setup apache to point localhost/analytics/ to port 3456. Open '/etc/apache2/apache.conf' in your favorite editor and add these lines: | + | Now to setup apache to point localhost/analytics/ to port 3456. Open '/etc/apache2/apache.conf' (or another conf location) in your favorite editor and add these lines: |
RewriteEngine On | RewriteEngine On | ||
| Line 42: | Line 46: | ||
ServerAdmin coge.genome@gmail.com ServerName localhost | ServerAdmin coge.genome@gmail.com ServerName localhost | ||
#ServerAlias geco.com.analytics | #ServerAlias geco.com.analytics | ||
| − | ErrorLog /home/rchasman/logs/error.log CustomLog <PATH>/logs/access.log combined LogLevel warn | + | ErrorLog /home/rchasman/logs/error.log CustomLog <PATH>/logs/access.log combined LogLevel warn |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
ProxyPass /analytics/ http://localhost:3456/analytics/ | ProxyPass /analytics/ http://localhost:3456/analytics/ | ||
| − | + | ||
| − | + | ||
ProxyPass /analytics http://localhost:3456/analytics/ | ProxyPass /analytics http://localhost:3456/analytics/ | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
</VirtualHost> | </VirtualHost> | ||
| − | + | These lines proxy calls to /analytics and /analytics/ to port 3456/analytics so that we don't have to type any ugly numbers to reach our site. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | Finally: | |
| − | + | $ sudo services apache2 restart | |
| − | + | If it says OK, it means the server should be started and you should be able to point a browser at it. | |
| − | + | If everything was configured properly point your browser to <DNS>/analytics and Analytics should be up and running! <br> <br> | |
Latest revision as of 17:29, 3 June 2016
CoGe Analytics is a metrics and analytics engine for the CoGe platform written on Clojure's web framework Noir.
Contents
How To: Deploy on a Server via Apache Webserver
Prerequisites:
(You can install these CLI tools using your linux distributions preferred package manager)
- Apache2 - with plugins
- libapache2-mod-proxy-html - For proxying the running port to the correct endpoints.
- libxml2-dev
- Maven - For Clojure Dependencies
- Git - For cloning repos in from github
- Leingingen - Leiningen - Automate Clojure projects without setting your hair on fire.
Configuring Analytics to the Database
Once you have all the prerequisites installed, you need to get the Greentea (Analytics) repo from Github. Run:
$ git clone https://github.com/LyonsLab/Greentea.git
Get Analytics Running:
Install Teabag to get Greentea running.
---Alternatively---
Inside the cloned directory run:
$ lein run &> /dev/null &
Leiningen should pull in all the required dependencies* and start a Jetty servlet running on port 3456.
Check localhost:3456 to verify that the analytics platform is running.
Configure Apache to Proxy the Servlet Port to the /analytics Endpoint
Now to setup apache to point localhost/analytics/ to port 3456. Open '/etc/apache2/apache.conf' (or another conf location) in your favorite editor and add these lines:
RewriteEngine On
NameVirtualHost *:90
Listen 90
<VirtualHost *:90>
ServerAdmin coge.genome@gmail.com ServerName localhost
#ServerAlias geco.com.analytics
ErrorLog /home/rchasman/logs/error.log CustomLog <PATH>/logs/access.log combined LogLevel warn
ProxyPass /analytics/ http://localhost:3456/analytics/
ProxyPass /analytics http://localhost:3456/analytics/
</VirtualHost>
These lines proxy calls to /analytics and /analytics/ to port 3456/analytics so that we don't have to type any ugly numbers to reach our site.
Finally:
$ sudo services apache2 restart
If it says OK, it means the server should be started and you should be able to point a browser at it.
If everything was configured properly point your browser to <DNS>/analytics and Analytics should be up and running!
