support https dev webserver

Outline

The goal of this task is to support https in the local dev webserver, such that if the option https: true in config/webserver.js is set to true, then the webserver server will be available as https instead of http. Services that need cors should have their settings updated accordingly.

Acceptance Criteria

• adding https: true to config/webserver.js should start the webserver in https
• if this setting is on, then any services that use ‘auto’ in their cors/whitelisting settings should use https instead of http. (e.g geth)

[StevenJNPearce]

@ryan-shea I’ve ‘Stopped Work’ on gitcoin for this issue - I just didn’t have the time to work on it the last few weeks. This will now be back to ‘open’ on gitcoin so someone else can pick it up. To whoever wants to work on it, refer to my commit here: https://github.com/StevenJNPearce/embark/commit/f959bf290dbd52ee10020c7b3c88698f2cf95a75

Most of the work is done there, so, you could use that as a starting point. Open blockchain.json, add https: true, key: /home/username/server.key, cert: /home/username/server.cert. It just needs a proxy implemented to talk to geth.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 180.0 DAI (180.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @pvgupta24.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $44,469.85 more funded OSS Work available on the Gitcoin Issue Explorer