Open recluse4615 opened 1 year ago
Idea for the "but i can understand some concerns regarding it": If you add it in the "Javascript API" way, then you can add a setting to enable/disable auto updates.
creating an auto updater itself is not an issue, outside of storing private keys
only the organisation should be able to "sign" new releases, that's ultimately the point of creating this under an org-space rather than an individual-space - if i lose interest in the project, mtlauncher itself shouldn't die
for now we can just store a json file in the repo which gets referenced by mtlauncher, this could be slow/have issues with geolocation/etc but it's the "easiest" way
in the future, we will automate the remote server by hosting a sveltekit site, probably on cloudflare pages or something (again, org-space rather than individual-space) that periodically reads the releases on github and parses it
this is probably the last major thing i want to do, so it's the "lowest" priority ahead of a v1 launch
tauri allows an auto updater to exist, which can effectively just query a file on GH to check if a newer version exists
it would be nice to not have to bother people to install new versions, but i can understand some concerns regarding it