You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to see support for HTTPS on local server, and not only HTTP.
I already have a partially working solution on my environment.
The only challenge is to make a choice about how to generate a self-issued certificate during the generation.
The text was updated successfully, but these errors were encountered:
Hey @wictorwilen,
Talking about adding support for HTTPS, I already updated the code templates in my own branch, but I'd like to also generate a self-signed certificate for SSL hosting. However, there are multiple options to do that (dotnet, PowerShell, OpenSSL, etc.). What is your preference? Or do you rather prefer to just prompt the developer for the path and password of the PFX, without generating it within the generation process? Thanks.
The only preference I have is that it should not require any additional installs, if not needed. I think it would be great to have a custom task that creates the certificate (could be done via the selfsigned npm package) and also documentation on how to provide your own.
I'd like to see support for HTTPS on local server, and not only HTTP.
I already have a partially working solution on my environment.
The only challenge is to make a choice about how to generate a self-issued certificate during the generation.
The text was updated successfully, but these errors were encountered: