[docs] Docs for Updater Module Missing?

[brifiction]

Hello Tauri Community!

I am learning Tauri product for the first-time, and note, very new to Rust too.

I was looking up your documentation to answer below:

How do I integrate update capabilities for my Tauri app? For example, 'Version 2.0.0 is out now! Click to update!'

Also in summary:

1. Is there a third-party service to host your Tauri desktop app for downloading?
2. Can we host our own service for visitors to download our Tauri desktop app? And to push new app versions out automatically? Similar to an 'Apple Store' or 'Google Play Store'?

I found this page here, https://tauri.studio/docs/api/js/modules/updater#updater but the markdown link is broken or not found. The Docusaurus search bar is not helping thus far with the current search results, is this page located elsewhere or have been renamed?

Lastly, additional resource links regarding how I can answer my question above would be great. Making your own desktop app available for download (and pushing version updates) will be awesome!

[JonasKruckenberg]

The link you mentioned changed to https://tauri.studio/api/js/modules/updater
Other than that, you can find general information about the updating process here: https://tauri.studio/guides/distribution/updater

Regarding your questions:

1. Is there a third-party service to host your Tauri desktop app for downloading?

Many small projects just use GitHub releases for this purpose, but as your userbase (hopefully 😁) grows you will have to use something like AWS buckets, as GitHub Releases is pretty slow.

2. Can we host our own service for visitors to download our Tauri desktop app? And to push new app versions out automatically? Similar to an 'Apple Store' or 'Google Play Store'?

Yes very much so, that's what this is designed for. You build new artifacts in CI, push then to your server and it then distributes the updates.

Edit: To clarify things a bit for you: Downloading an app the first time and updating are completely separate actions.
Tauri uses a self updater which basically means the app replaces itself with the new version. This is the default pattern on desktop and it's different to the managed updating of mobile OS'es. In the latter an app doesn't know anything about updates, it gets replaced by the OS.

The important thing to know is that a Tauri app doesn't care at all where it came from. You can distribute it via USB stick, your own server, GitHub releases, AWS, ... it doesn't matter.

When it comes to updating however, it does matter as you need some https endpoint your app can check for updates.

So when we distribute an app, we usually treat updates and "normal" builds completely differently

[brifiction]

Thanks a bunch @JonasKruckenberg for the swift reply, much appreciated 😃 !

Noted, valuable and informative points you've shared, for me to digest. Especially about your answer for Question 2, and including your Edit (additional tip) portion.

Anyway, very much appreciated 😃 I'll have to approach my Tauri app project step by step moving forward 😅

Lastly, you've answered my initial question above, the two correct docs links have been noted - cheers! Have a good one!