Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PullRequest: Implementation #10700

See original GitHub issue

PR

#10700 - HTTPS via ENV

Additional Issues

Scenario 1 https default cert invalid => simply host a proxy with a valid cert and let him accept the other same for browser simply add the exemption local
Should ship default cert generation can not be guaranteed but we could offer a script for that anyway

Current Impl branch

Documentation

# Using Own Key relativ to process.cwd
# if SSL_CRT_FILE && SSL_KEY_FILE HTTPS=ture
HTTPS=true SSL_CRT_FILE=cert.crt SSL_KEY_FILE=cert.key

# Using Self Signed Cert that gets generated if it does not exist
# Using shipped developer Self Signed Cert 
HTTPS=true

Generate a cert and key delete the cert request.

openssl genrsa -out key.pem
openssl req -new -key key.pem -out csr.pem
openssl x509 -req -days 9999 -in csr.pem -signkey key.pem -out cert.pem
rm csr.pem

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

frank-dspeedcommented, May 30, 2020

Sorry but when I do a PR I want to do it right as I am a senior-level engineer. I understand the side effects of such implementations before I even do them so I try to figure out all edge cases

0reactions

balazsorban44commented, Jan 30, 2022

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.