How to use as dependency with continuous integration environment about https-localhost HOT 5 CLOSED

Hi! Thank you for opening an issue!

https-localhost was designed for local use, on your PC, and not for production or for CI.
Anyway, if you could explain better the goal you want to reach with https-localhost on Jenkins I'll be glad to help you to find a workaround, also by adding some checks in the script.

First please note the issues #8 and #10. I'm planning to implement them this week.
Now the script acts this way: at install time the post install script generates certificates in ./certs.
Then, the script will do: nothing at install time (your first goal reached 🎉) and at first run generates certificates in ~/.https-localhost.

At this point, your problem at install time will be solved but is moved at run time. Furthermore, if you run https-localhost on linux you will be asked for sudo password also for the 443 and 80 ports (#11).

The workaround for the latter is easy: if you are able to change the port, using a higher number (like 4443 and 8080) the problem is solved. Check out the README.

For the first problem (certificates generation) I need further information:

1. You are running under root on Jenkins? If not, is a problem to run the script under root?
2. Do you need the certificates to be trusted (the green lock in the image)? Or you just need to serve your content over https, and doesn't matter if the certificate is valid or not?

from https-localhost.

Thanks for your reply. Yes, I think as long as an npm install won't cause it to ask for a password my issue will be solved. I don't need to use the certificates for anything that I am doing with Jenkins. I just need to npm install and build the app. Other Jenkins users might need to use the certificates and I would assume that they are not running under root. I think it would be nice if the certificates were trusted so that it works without having to disable certificate checking.

from https-localhost.

I'm working on that, I think it will be ready for the end of the next week.

Is not possible to trust certificates without root permissions, but I'll add an option to use a custom certificate, so that the certificates generation will be skipped.

from https-localhost.

Should be solved with #13. Just upgrade your dependency to v4.1.0. Let me know!

from https-localhost.

Closed. Feel free to open again if you have any problem with the proposed solution.

from https-localhost.