Skip to content

AtlasOfLivingAustralia/tepapa-hub

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This hub is no longer being supported

tepapa-hub Build Status

Deploying a new version of tepapa-hub to Nexus

Before deploying a new version, check that the biocache-hubs dependency version is up to date in grails-app/conf/BuildConfig.groovy.

Travis-CI is used to deploy new versions of tepapa-hub to Nexus. This is done automatically by updating the version number in the application.properties file and pushing to GitHub.

Once the new version of tepapa-hub is deployed to Nexus, the version number in ansible-inventories needs to change. To do this, the version number must be changed in:

https://github.com/AtlasOfLivingAustralia/ansible-inventories/blob/master/livingaotearoa.ala.org.au

If the biocache_hub_version is commented out then presumably it will use the most recent version it can find.

Deploying the current Nexus deployed version of tepapa to a virtual machine

If you have not yet installed Ansible, Vagrant, or VirtualBox, use the instructions at the ALA Install README.md file to install those first for your operating system.

Then, to deploy tepapa onto a local virtual box install use the following instructions:

$ cd gitrepos
$ git clone [email protected]:AtlasOfLivingAustralia/ala-install.git
$ (cd ala-install/vagrant/ubuntu-trusty && vagrant up)

Add a line to your /etc/hosts file with the following information, replacing '10.1.1.3' with whatever IP address is assigned to the virtual machine that Vagrant starts up in VirtualBox:

10.1.1.3 livingaotearoa.ala.org.au

Then you can clone the ansible instructions and install it onto the given machine:

$ git clone [email protected]:AtlasOfLivingAustralia/ansible-inventories.git
$ ansible-playbook -i ansible-inventories/livingaotearoa.ala.org.au ala-install/ansible/tepapa-hub-standalone.yml --private-key ~/.vagrant.d/insecure_private_key -vvvv --user vagrant --sudo

Deploying to AWS EC2 production server

After testing locally, the same ansible scripts can be used to deploy to the production server which is an AWS EC2 server.

Comment out any testing line for livingaotearoa.ala.org.au in your /etc/hosts file and add the following line:

52.63.44.128 livingaotearoa.ala.org.au

Then deploy to that machine using the following command, replacing "MY_USER_NAME" with your login username:

$ ansible-playbook --user MY_USER_NAME -i ansible-inventories/livingaotearoa.ala.org.au ala-install/ansible/tepapa-hub-standalone.yml --private-key ~/.ssh/id_rsa -vvvv --sudo --ask-sudo-pass