Deployment¶
Deployment is done in the System Health Lab VPS, refer to this documentation anything about connecting to the VPS and registering services in Binchicken.
Running services with Docker / Deployment of Website¶
The development and production services are handled with Docker. The services that will run in production is defined in the docker-compose-prod.yml. Make sure that you have .env file in the same directory as the repository before proceeding.
Redeployment
Whenever changes are made, you can connect to the VPS instance, and go to the place where this repository can be found. Run git pull to fetch the newest change, and then Either run the redeploy.sh or type
1 | |
Services in Production
The client-side and server-side applications are hosted in the VPS. You may need a Mongo Database. This is currently hosted in Atlas Mongo (ask Frinze for details. He will be happy to help.). The details of the connection to the database should be in the .env file.
Deployment of Documentation¶
This is deployed in Github Pages. See CI Pipeline documentation.
Domain Name¶
The domain name is essentially just a holder for a specific URL name. Using your DNS provider such as NameCheap or Cloudflare (when you connect the domain name with the UWA proxy). Direct the traffic in the domain name (cf02.next-dc.uwa.edu.au if using Cloudflare).
Additional Information
The setup with the VPS, NGINX/Binchicken and Domain Name is done only once on setup. Any future deployment, you just need to use the documentation in the previous section.