Skip to content

add update mechanism #60

@ThatNerdSquared

Description

@ThatNerdSquared

reasoning

  • we can’t update the app in the future without an updater mechanism, unless we get people to manually re-download and replace the app, which probably won’t get a lot of cooperation because:
    1. people are lazy
    2. people are used to everything else having autoupdate

implementation ideas

  • i’m not sure if there’s an existing package we can use here, if there’s a good one we might be able to just plug one in. it also doesn’t seem too difficult to build a simple one.
    • updater should be separate binary so it can delete/add new daemon + gui
  • the updater will likely need to contact some outside service to check if the current app version is still the latest one
    • for each build, store the app version number in the Config
  • ideally, this is just “curl this GitHub URL” or something like that so we don’t need to run our own servers
  • if we do need to run our own server-side tech to store the latest version number or something, i would stick this onto a cloudflare worker or some other serverless platform so we don’t need to pay for it.
  • it’s also dead simple to just return a singular version number string so, shouldn’t be too hard to build/maintain

Created via Raycast

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions