-
Notifications
You must be signed in to change notification settings - Fork 1
Deploying
Ensure you lodge a PR that gets approval from one of the admins into the develop branch. After this is squash-merged via github, and the build successfully deploys to dev
. dev
can be merged into master for deployment.
Please follow below steps:
git checkout dev
git fetch && git pull origin dev
git checkout master
git pull origin master
git reset --hard dev
npm version [major,minor,patch]
git push origin master --force --tags
How it works:
The app is built to the ./dist/public
directory, and zipped. Azure's zip upload endpoint is used to upload and unzip to the public
directory so it can be served by the backend. Docs are here.
Note: the recommended API for deployment is zipdeploy. This is used for the backend; it cannot be used for frontend also because it wipes the previous deployment.
The parent directory of public
is where the API repo is deployed to using zipdeploy.
deploy.sh
requires user credentials in the environment variables. Read about creating/updating user credentials here.