-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use localhost OpenVSX instance in VSCode #979
Comments
Answering my own question: you can configure Node/Electron to ignore cert errors globally with a command-line argument. In other words, launch VSCode like this: code --ignore-certificate-errors This is sufficient for my needs as I am just after a fully integrated dev environment on my machine. It might be nice to include this info in a doc somewhere... |
Hi @opennano, looking forward to your PR. |
Title: Suggesting Changes to OpenVSX Wiki: HTTPS Deployment I have made some updates to the Wiki related to deploying OpenVSX with HTTPS. Specifically, I added a new section on how to deploy OpenVSX via HTTPS using a self-signed certificate and Nginx. You can review my changes in my fork here: branch: fix-http-to-https-Oliver Here are the key points in my changes: Added instructions for applying for a self-signed certificate using OpenSSL. Looking forward to your feedback! Best regards, |
Is there any way to integrate these two locally? VSCode refuses to talk to http://localhost:8080 where the server is running. It at least tries to connect if I point it to https locally (i.e. Nginx proxy-passing from https://localhost:8443 to http://localhost:8080), but then I can't find any solution to get it to stop complaining about the self-signed cert I had to generate for Nginx.
Anyone ever gotten this to work? It sure would be nice to not have to deploy a whole server with valid certs for a simple poc.
The text was updated successfully, but these errors were encountered: