david/net-base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

update readme

Browse Source
This commit is contained in:
David Claeys
2025-04-01 12:39:27 +02:00
parent db538746ff
commit cd017a458a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -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.
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).
And depending on your use-case you event might consider to use docker networking in order to accomplish proper isolation.