Merge pull request #140 from johanherman/arteria-staging

Add a note to README on how to deploy Arteria staging services

README.md

@@ -85,6 +85,21 @@ We can now, still standing in `/lupus/ngi/irma3/deploy`, do a `git fetch --tags
 
 Run `python sync.py production` to rsync all files under `/lupus/ngi/production` from irma3 to irma1. 
 
+#####Arteria staging 
+
+Due to the special setup on Irma there is some extra work at the moment when deploying and running a staging version of the Arteria services. So until the Arteria roles have been refactored one have to deploy a staging env with Arteria staging vars set correctly for the services to start. I.e. do something like:  
+
+```
+ansible-playbook install.yml -e arteria_checksum_environment=staging -e arteria_siswrap_environment=staging -e deployment_environment=staging -e deployment_version=arteria-staging-FOO
+python sync.py staging
+```
+
+And then inside a screen on irma1 start two windows with the corresponding commands: 
+
+```
+/lupus/ngi/staging/latest/sw/arteria/siswrap_venv/staging/bin/siswrap-ws --configroot=/lupus/ngi/staging/latest/conf/arteria/siswrap/staging/ --port=10431 --debug
+/lupus/ngi/staging/latest/sw/arteria/siswrap_venv/staging/bin/siswrap-ws --configroot=/lupus/ngi/staging/latest/conf/arteria/siswrap/staging/ --port=10431 --debug
+```
 ####Nota bene
 
 Remember that you will probably have to restart services manually after a new production release have been rolled out. First re-load the crontab as the func user on irma1 with a `crontab /lupus/ngi/production/latest/conf/crontab_SITE`. Then, depending on what software your func user is running, continue with manually shutting down the old versions and re-start the new versions of the software.