update readme
This commit is contained in:
		| @@ -80,7 +80,7 @@ If you want to directly expose the Kestrel webserver use the following environme | ||||
|   - **ASPNETCORE_Kestrel__Certificates__Default__KeyPath** (the path to the certificate) | ||||
|   - **ASPNETCORE_Kestrel__Certificates__Default__Password** (the password for the key file) | ||||
|  | ||||
| The certificate included by default (generated trhough the _dotnet dev-certs_ command) is not really suited for production environments. | ||||
| The certificate included by default (generated through 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).  | ||||
| Depending on your use-case you event might consider to use docker networking in order to accomplish proper isolation. | ||||
		Reference in New Issue
	
	Block a user