Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regular https directory backend #74

Open
sigaloid opened this issue Jul 10, 2021 · 2 comments
Open

Regular https directory backend #74

sigaloid opened this issue Jul 10, 2021 · 2 comments

Comments

@sigaloid
Copy link

Would it be possible to have a regular https directory backend with a json file describing the release? I think this would be more service-agnostic.

@jaemk
Copy link
Owner

jaemk commented Jul 12, 2021

Yeah that would be possible. Would you mind describing a bit more how you would expect that to work?

@sigaloid
Copy link
Author

Similar to NetSparkle's appcast, a JSON/RON file could contain the new releases, and that file's directory could contain the install files. For example:

example.net/update/manifest.json -> file containing new versions, different architectures, etc
example.net/update/app-1.0.0-win64.exe
example.net/update/app-1.0.0-linux
example.net/update/app-1.0.1-win64.exe
...etc

And each file is described in the manifest.json, which is updated as another release is made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants