#Updater endpoint when using static JSON file

8 messages · Page 1 of 1 (latest)

tall rain
#

Hi, I'm following the documentation for configuring the updater. It mentions using variables in the endpoints field that get substituted when the actual request is made (ex: {{current_version}}). Is there any benefit to using these variables if I'm simply hosting a static JSON file in S3 (as opposed to hosting an update server)?

I'm thinking of having an endpoint like https://downloads.acme.com/releases/latest/updates.json so that every client would just point to the latest and greatest version available. That sounds fine, but I just wanted to make sure I wasn't missing anything since the example in the docs uses those variables. Thanks!

latent goblet
#

there are two ways to do it, either with a default dialog updater where you give the json with the latest update

#

or with a server and each app

#

(windows, macos, linux) can request and get back only the needed info using in the url {{current_version}} and {{platform}} {{arch}} etc!

#

I am using this with my default dialog and it works great

tall rain
#

Cool thanks. I have it working but I wanted to see if there was a recommended way of hosting the static JSON file. As in /darwin/v1.0.0/updater.json vs. /releases/latest/updater.json.

Probably just makes the most sense to have a single JSON file that lists all platforms - no need for any of those variables.

latent goblet
#

I think the yse of {{current_version}} and the rest is if you want custom logic in your app to determine if you want to install beta or alpha or pre-release/release etc and thus you would need your app to have custom code and a server to fetch the specific binary you want