Skip to content
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.

Deploy Procedures

Mike Caprio edited this page Jun 27, 2017 · 5 revisions

Dev Deploy

The first step of staging a deployment to development is to make sure that the master branch is ready for a release from the dev branch. When your dev branch is ready, follow the instructions below to merge master into dev (which keeps the master branch clean):

(on branch development)$ git merge master
(resolve any merge conflicts if there are any)
git checkout master
git merge --no-ff development

Now that master is ready to deploy, go to the dev server and stop the API service in systemd (you must have sudo):

sudo /bin/systemctl stop nodejs-api.service

Next run:

cd API-Portal
git pull origin master

Finally start the API in systemd:

sudo /bin/systemctl start nodejs-api.service

The API should now be running, and the web server should already be pointing at it on http://api-dev.library.amnh.org. Please note this URL is currently only available to you if you are on internal AMNH networks.

Production Deploy

Please contact IT to schedule a production deploy using standard call center procedure. When the dev server is tested and ready, IT will mirror dev into production at the URL http://api.library.amnh.org/. Please note this URL is currently only available to you if you are on internal AMNH networks.

Clone this wiki locally