From eab726d4df9ff037b9819f76ba9ac60bbd4507c1 Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Mon, 25 May 2026 06:09:23 +0000 Subject: [PATCH] docs: document automatic HTTPS certificate generation for non-.NET AppHosts Documents the new behavior introduced in microsoft/aspire#17454: - When aspire run starts a non-.NET AppHost (e.g., TypeScript) in non-interactive mode and no HTTPS dev certificate exists, the CLI now automatically generates one. - The ASPIRE_CLI_GENERATE_HTTPS_CERTIFICATE environment variable can be set to 'false' to opt out of automatic certificate generation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../docs/app-host/certificate-configuration.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/frontend/src/content/docs/app-host/certificate-configuration.mdx b/src/frontend/src/content/docs/app-host/certificate-configuration.mdx index 924c7339f..ec20737a7 100644 --- a/src/frontend/src/content/docs/app-host/certificate-configuration.mdx +++ b/src/frontend/src/content/docs/app-host/certificate-configuration.mdx @@ -38,6 +38,18 @@ Many of the certificate features in Aspire rely on a development certificate. Be The preferred way to manage the development certificate is to use the [Aspire CLI](/get-started/install-cli/). When you run `aspire run`, the CLI automatically ensures the development certificate is created and trusted. No additional manual steps are required. +For non-.NET AppHosts (such as [TypeScript AppHosts](/app-host/typescript-apphost/)), the `dotnet` first-run experience that normally creates the HTTPS development certificate does not run. The Aspire CLI handles this automatically: when `aspire run` starts a non-.NET AppHost in non-interactive mode and no HTTPS development certificate exists, the CLI generates one. If generation fails, a warning is displayed but the run continues. + +To opt out of automatic certificate generation, set the `ASPIRE_CLI_GENERATE_HTTPS_CERTIFICATE` environment variable to `false`: + +```bash title="Disable automatic HTTPS certificate generation" +ASPIRE_CLI_GENERATE_HTTPS_CERTIFICATE=false aspire run +``` + +```powershell title="Disable automatic HTTPS certificate generation (PowerShell)" +$env:ASPIRE_CLI_GENERATE_HTTPS_CERTIFICATE="false"; aspire run +``` + You can also manage certificates explicitly with the Aspire CLI: ```bash title="Trust the development certificate"