From cd017a458a5aff78a4dc678720f93da5f5fe146f Mon Sep 17 00:00:00 2001 From: David Claeys Date: Tue, 1 Apr 2025 12:39:27 +0200 Subject: [PATCH] update readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bfb0fdf..9cdb6b0 100644 --- a/README.md +++ b/README.md @@ -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. \ No newline at end of file