Skip to content

Commit

Permalink
Add information about windows certificate.
Browse files Browse the repository at this point in the history
  • Loading branch information
Luxapodular committed Apr 15, 2020
1 parent 5aac6ae commit fbfb7f7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand All @@ -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.
Expand Down

0 comments on commit fbfb7f7

Please sign in to comment.