update build

2026-06-25 09:09:48 +02:00
parent 13ecfe5494
commit 64d72d6c2d
2 changed files with 51 additions and 8 deletions
@@ -93,8 +93,17 @@ Depending on your use-case you event might consider to use docker networking in
 The included certificate is generated through the _dotnet dev-certs_ command. This is a very convenient and suitable way to generate development certificates through the dotnet SDK.

 The password used to generate the certificate is randomly generated through the `openssl rand -base64 12` at build time.
-The build agent used for the build is hosted on my own infrastructure but I don't have any access to it (neither do I intend to do so).<br/>
-However if you feel uncomfortable with this fact, feel free to build the image yourself.
+If you inspect the image layers you'll able to easily see it.
+I think this is fine for development purposes and just want to get things up and running, although this is not recommended for production use at all.
+You can generate your own password and certificates in the following way :
+
+```sh
+# generate a random secure password
+openssl rand -base64 12
+# use the .net cli to generate your own certificates with your chosen password
+dotnet dev-certs https --export-path /config/aspnetapp.pem --password "YOUR PASSWORD" --format PEM
+```
+After this you only need to map your own certificates with the **ASPNETCORE_Kestrel__Certificates__** variables.

 ### Versioning