Skip to content

Commit 5667cbe

Browse files
authored
Update updater.mdx (#2751)
1 parent 90ad6ac commit 5667cbe

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

src/content/docs/plugin/updater.mdx

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -193,11 +193,12 @@ On Windows, Tauri will create .zip archives from the MSI and NSIS installers ins
193193

194194
Set up the `tauri.conf.json` in this format for the updater to start working.
195195

196-
| Keys | Description |
197-
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
198-
| `createUpdaterArtifacts` | Setting this to `true` tells Tauri's app bundler to create updater artifacts. If you're migrating your app from an older Tauri version, set it to `"v1Compatible"` instead. **This setting will be removed in v3** so make sure to change it to `true` once all your users are migrated to v2. |
199-
| `pubkey` | This has to be the public key generated from the Tauri CLI in the step above. It **cannot** be a file path! |
200-
| `endpoints` | This must be an array of endpoint URLs as strings. TLS is enforced in production mode. Tauri will only continue to the next url if a non-2XX status code is returned! |
196+
| Keys | Description |
197+
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
198+
| `createUpdaterArtifacts` | Setting this to `true` tells Tauri's app bundler to create updater artifacts. If you're migrating your app from an older Tauri version, set it to `"v1Compatible"` instead. **This setting will be removed in v3** so make sure to change it to `true` once all your users are migrated to v2. |
199+
| `pubkey` | This has to be the public key generated from the Tauri CLI in the step above. It **cannot** be a file path! |
200+
| `endpoints` | This must be an array of endpoint URLs as strings. TLS is enforced in production mode. Tauri will only continue to the next url if a non-2XX status code is returned! |
201+
| `dangerousInsecureTransportProtocol` | Setting this to `true` allows the updater to accept non-HTTPS endpoints. Use this configuration with caution! |
201202

202203
Each updater URL can contain the following dynamic variables, allowing you to determine server-side if an update is available.
203204

@@ -479,7 +480,7 @@ mod app_updates {
479480

480481
let update = app
481482
.updater_builder()
482-
.endpoints(vec![url])
483+
.endpoints(vec![url])?
483484
.build()?
484485
.check()
485486
.await?;
@@ -613,7 +614,7 @@ let update_url = format!("https://{channel}.myserver.com/{{{{target}}}}-{{{{arch
613614

614615
let update = app
615616
.updater_builder()
616-
.endpoints(vec![update_url])
617+
.endpoints(vec![update_url])?
617618
.build()?
618619
.check()
619620
.await?;

0 commit comments

Comments
 (0)