Jump to content

Emby Beta Releases Github API Path


ssg99si

Recommended Posts

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

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

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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...