update readme

This commit is contained in:
David Claeys 2025-04-01 12:40:28 +02:00
parent cd017a458a
commit 3a75c0af5e

View File

@ -34,4 +34,4 @@ However you never should use the included development certificate if you want to
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. Depending on your use-case you event might consider to use docker networking in order to accomplish proper isolation.