fix #451 testing certs for windows

[Grommers00]

Issue This PR Addresses

#451 fixed for windows certs.

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

This installs openssl on our travis CI, and then runs a shell script that should generate the scripts needed to create our own certificates.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

Travis CI is run on the github repository, so it will be using the travis ci build here to do the testing.

[humphd]

I looked at the build logs for Windows, and I see this:

mkdir: cannot create directory 'certs': File exists

I didn't see any output for the ./tools/generate-ssl-certs.sh command, maybe that's OK?

Do we have any other way of knowing if this worked or not?

[Grommers00]

I looked at the build logs for Windows, and I see this:

mkdir: cannot create directory 'certs': File exists

I didn't see any output for the ./tools/generate-ssl-certs.sh command, maybe that's OK?

Do we have any other way of knowing if this worked or not?

It's hard because windows would open that in a separate window, that might not show in a Travis CI environment as it would be running in a subsystem of itself.

[humphd]

Looks good from a CI and code point of view. Can we get a Windows dev to test this locally?

Also, @Grommers00, either in this PR or another issue you file, can we add docs on this bit? People on Windows can follow the same steps as you are doing in CI to get this to work locally.