From fbfb7f72a7cb255e9cefea3db30a81de6a93029e Mon Sep 17 00:00:00 2001 From: Luca Damasco Date: Wed, 15 Apr 2020 14:47:41 -0400 Subject: [PATCH] Add information about windows certificate. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c160862f7..a5937add6 100644 --- a/README.md +++ b/README.md @@ -125,7 +125,7 @@ You'll need: 1) An API Key ID 2) An API Key Issuer ID -3) A certificate .p8 file saved to your ~/private_keys directory. +3) A Windows Code Signing certificate (.p12 file) saved to your ~/private_keys directory and password. 4) A Developer ID Application Certificate (Saved to your keychain). 5) A Developer ID Installer Certificate (Saved to your keychain). @@ -135,7 +135,7 @@ We obtained code signing certificates from [SSL.com](https://www.ssl.com). Reach Step 1. Building: -1.1) Run `API_KEY_ID="..." API_KEY_ISSUER_ID="..." npm run build-packages` +1.1) Run `API_KEY_ID="..." API_KEY_ISSUER_ID="..." WIN_CSC_LINK="~/PATH/TO/CERTIFICATE.p12" WIN_CSC_KEY_PASSWORD="PASSWORD" npm run build-packages` Ensure you provide the correct API key information as variables, or the Mac applications will not properly sign and notarize. If the certificates are installed correctly, they should automatically be used.