Skip to content
This repository has been archived by the owner on Sep 19, 2023. It is now read-only.

Latest commit

 

History

History
55 lines (36 loc) · 1.9 KB

DEPLOY-POST.md

File metadata and controls

55 lines (36 loc) · 1.9 KB

Post VM Deployment

Procedure to perform on VM after all setups are done.

Setup Continuous Delivery

This must be done after completed establishing the CI pipeline.

  1. Go to VM page.
  2. Go to Settings > Continuous Delivery at the left panel.
  3. Configure as needed.
  • Deployment group should be something like DL Site Front Deployment Group

This mainly does the VM - Azure Pipelines linking work, so that the CD created in the future can use the deployment group linked in step 3.

Configure DNS

Use an unused submodain first to check if the app is public.

  • Temporarily add the unused host name as domain_name in nginx config

Using domain address (example.com)

This is configured during initial VM deployment.

  • Set the domain address as CNAME record.
    • Name is the subdomain.
    • Content is the configured domain address.

For example, if the configured DNS is example.com and the domain is domain.com, setting Name as subdomain and Content as example.com allows the user on the internet to connect to the VM using subdomain.domain.com.

Using static IP (10.0.0.1)

Use domain address whenever it's possible to increase security.

  • Set the IP address as A record.
    • Name is the subdomain.
    • Content is the IP of the VM.

For example, if the IP of the VM is 10.0.0.1 and the domain is domain.com, setting Name as subdomain and Content as 10.0.0.1 allows the user on the internet to connect to the VM using subdomain.domain.com.

Create util aliases

Copy the file samples/.bash_aliases to the root directory of deploy. The file should located at /home/deploy/.bash_aliases.

After this, run source .bashrc to load the changes.

This adds a command fm which simply output the current free RAM %.