From d41cb0a5cda2b0bcdd1fc59af97d5d11f11fe4d9 Mon Sep 17 00:00:00 2001
From: Kalila L <kasenvr@gmail.com>
Date: Mon, 24 Aug 2020 15:27:56 -0400
Subject: [PATCH] Update Install.md instructions for code signing.

---
 INSTALL.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/INSTALL.md b/INSTALL.md
index af398ee6b3..4307ddc79e 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -1,5 +1,7 @@
 # Creating an Installer
 
+*Last Updated on August 24, 2020*
+
 Follow the [build guide](BUILD.md) to figure out how to build Vircadia for your platform.
 
 During generation, CMake should produce an `install` target and a `package` target.
@@ -13,6 +15,8 @@ To produce an installer, run the `package` target. However you will want to foll
 
 #### Windows
 
+##### Prerequisites
+
 To produce an executable installer on Windows, the following are required:
 
 1. [7-zip](<https://www.7-zip.org/download.html>)  
@@ -59,6 +63,12 @@ To produce an executable installer on Windows, the following are required:
 1. [Node.JS and NPM](<https://www.npmjs.com/get-npm>)
     1.  Install version 10.15.0 LTS
     
+##### Code Signing (optional)
+
+For code signing to work, you will need to set the `HF_PFX_FILE` and `HF_PFX_PASSPHRASE` environment variables globally.
+
+##### Creating the Installer
+    
 1.  Perform a clean cmake from a new terminal.
 1.  Open the `vircadia.sln` solution with elevated (administrator) permissions on Visual Studio and select the **Release** configuration.
 1.  Build the solution.