-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: persist generated https certificates #132
Labels
enhancement
New feature or request
Comments
Thanks for the idea! The default behavior of not persisting was kinda intentional to make sure warn users everytime about this and avoid possible local cert leaking problems but at least via an opt-in flag/option i think we can implement this feature 💯 |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
When using self-signed generated certificates for local development, every time you restart listhen (or in my case restart the nuxt dev server), a new certificate is generated and your browser's "Your connection is not private" page must be explicitly bypassed.
As a small optimization, it would be very nice if the generated certificates were (maybe optionally) persisted to disk so that you only need to manually bypass the browser's insecure warning page once (or each time a new certificate is generated). This is similar to how @vitejs/plugin-basic-ssl works by saving the cert inside of a hidden temp dir in your project's
node_modules
directory (./node_modules/.vite/basic-ssl
).I could see listhen doing something similar by persisting the certs at
./node_modules/.listhen/certs
.I'm not sure if this has security implications or may be unreliable depending on the runtime environment, so if this is impractical and/or unadvisable I completely understand. Thanks!
Additional information
The text was updated successfully, but these errors were encountered: