SANUS Deployment Process

Notes on Versioning

Legacy (2.x) versions are no longer tagged. Updating tags on 3.x follows the pattern below.

previous tag: 3.3.16
new beta tag: 3.3.17b1 (increment the last number for each beta before the next production push)
new production tag: 3.3.17

Step 1 – Merge changes into master

1.b – 2.x Project

# in your SANUS 3.x checkout directory 
git pull 
git checkout master 
git merge dev 
git describe --tags (this will give you the last tagged version) 
git tag (increment tag number) 
git push 
git push --tagsCode language: Bash (bash)

1.a – 3.x Project

# in your SANUS 2.x checkout directory 
git pull 
git checkout master 
git merge dev 
git pushCode language: PHP (php)

Step 2 – Beta deployment

su - deploy (password is disc5lock3seize) 
cd cap/sanus25 
./beta.sh 
:q [enter] 
cd ../cap/sanus3 
./beta.sh 
:q [enter]

Step 3 – Production Deployment

Wait to do this until you’ve been given direction from the project manager / interactive director. This won’t happen immediately after the beta deployment

# in your SANUS 3.x checkout 
git checkout master 
git describe --tags (to get the beta version number) 
git tag (the version string without the beta modifier) 
git push --tags su - deploy (password is disc5lock3seize) 

cd cap/sanus25 
./prod.sh 
:q [enter] 

cd ../cap/sanus3 
./prod.sh 
:q [enter]Code language: PHP (php)