Skip to content

[docs] Document automatic HTTPS certificate generation for non-.NET AppHosts #1063

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
aspire-repo-bot wants to merge 1 commit into from
Closed

[docs] Document automatic HTTPS certificate generation for non-.NET AppHosts #1063

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions src/frontend/src/content/docs/app-host/certificate-configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
Loading