ssg99si 4 Posted December 7, 2018 Share Posted December 7, 2018 Hello, So there's an API path on Github for Emby stable releases: https://api.github.com/repos/mediabrowser/Emby.releases/releases/latest However there isn't one for the beta releases, only this page: https://github.com/MediaBrowser/Emby.Releases/releases Can we get the same sort of API for beta releases? Thanks Link to comment Share on other sites More sharing options...
Luke 36884 Posted December 7, 2018 Share Posted December 7, 2018 Yes you can use the same api for beta releases. Link to comment Share on other sites More sharing options...
ssg99si 4 Posted December 7, 2018 Author Share Posted December 7, 2018 Hmm.. I do not see how. Is there any documentation or could you point me in the right direction? Link to comment Share on other sites More sharing options...
Luke 36884 Posted December 7, 2018 Share Posted December 7, 2018 Have you explored the prerelease property? Link to comment Share on other sites More sharing options...
ssg99si 4 Posted December 7, 2018 Author Share Posted December 7, 2018 I am not sure how to do that, could you link me to it please? Link to comment Share on other sites More sharing options...
Luke 36884 Posted December 7, 2018 Share Posted December 7, 2018 https://developer.github.com/v3/repos/releases/ Link to comment Share on other sites More sharing options...
ssg99si 4 Posted December 7, 2018 Author Share Posted December 7, 2018 I'm not sure that help me much. I am looking for a link similar to this: https://api.github.com/repos/mediabrowser/Emby.releases/releases/latest But for the beta/pre-releases Link to comment Share on other sites More sharing options...
Luke 36884 Posted December 7, 2018 Share Posted December 7, 2018 There is no such thing. Link to comment Share on other sites More sharing options...
ssg99si 4 Posted December 7, 2018 Author Share Posted December 7, 2018 Would something like that be possible to add? Or do you know if an auto-update for emby beta is coming? Link to comment Share on other sites More sharing options...
Luke 36884 Posted December 7, 2018 Share Posted December 7, 2018 There's nothing to add because we use the github api. We use whatever that has available. We currently only have auto-update on windows, but may investigate it for other platforms in the future. thanks. Link to comment Share on other sites More sharing options...
samuelqwe 313 Posted December 7, 2018 Share Posted December 7, 2018 (edited) Something like this? https://api.github.com/repos/mediabrowser/Emby.releases/releases This one should have all the releases, not just the stable versions Edited December 7, 2018 by samuelqwe Link to comment Share on other sites More sharing options...
ssg99si 4 Posted December 7, 2018 Author Share Posted December 7, 2018 Yes that is perfect, thanks! Link to comment Share on other sites More sharing options...
doonze 28 Posted December 7, 2018 Share Posted December 7, 2018 Yes, that works for getting beta. Just a word to the wise, that json is nestled on it's root layer. With python at least, that causes it's json reader to make the results a list of objects instead of a true dictionary. A list of dictionaries. So you have to access the nestled parts like a list, then access the data like a dictionary. Took me forever to figure out what it was doing. I'll have beta added to my linux autoupdater tonight, my brain is melted from list of dictionaries and I need sleep before coding anything! LOL Link to comment Share on other sites More sharing options...
doonze 28 Posted December 8, 2018 Share Posted December 8, 2018 EmbyUpdate v1.1 released with beta installing options. Github json isn't my favorite. On the linked /release API path above it puts whatever the most recent release is (beta or stable) into index 0, and moves the last release to index 1. So I had to create logic to run through the json (array in python) to find the most recent beta or stable release, and use that according to what the user specified they wanted. There is some weirdness where the newest beta releases are showing up in the API, however they are not listed as releases on Github. I'll have to ask Luke about that in my own thread. Just passing this on for anyone who finds this thread later and wants to save some time figuring out the Github API. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now