update readme
This commit is contained in:
parent
db538746ff
commit
cd017a458a
@ -31,7 +31,7 @@ This images uses the system provided by Microsoft to generate a development cert
|
|||||||
In previous .NET versions it was not recommended to expose Kestrel directly to the internet. Now Microsoft claims you can do that.
|
In previous .NET versions it was not recommended to expose Kestrel directly to the internet. Now Microsoft claims you can do that.
|
||||||
However you never should use the included development certificate if you want to do that.
|
However you never should use the included development certificate if you want to do that.
|
||||||
|
|
||||||
If you want to expose the Kestrel server you should use the *ASPNETCORE_Kestrel__Certificates__Default__Path*, *ASPNETCORE_Kestrel__Certificates__Default__KeyPath* and *ASPNETCORE_Kestrel__Certificates__Default__Password* variables to correclty setup a certificate. The _dotnet dev-certs_ command is not really suited for production environments.
|
If you want to expose the Kestrel server you should use the **ASPNETCORE_Kestrel__Certificates__Default__Path**, **ASPNETCORE_Kestrel__Certificates__Default__KeyPath** and **ASPNETCORE_Kestrel__Certificates__Default__Password** variables to correclty setup a certificate. The _dotnet dev-certs_ command is not really suited for production environments.
|
||||||
|
|
||||||
In practice it's much easier to expose the server through a proxy to the public (hence the recommended method).
|
In practice it's much easier to expose the server through a proxy to the public (hence the recommended method).
|
||||||
And depending on your use-case you event might consider to use docker networking in order to accomplish proper isolation.
|
And depending on your use-case you event might consider to use docker networking in order to accomplish proper isolation.
|
Loading…
x
Reference in New Issue
Block a user