-
Notifications
You must be signed in to change notification settings - Fork 31
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
Notify of updates #12
Comments
I really like and find it useful. |
So, you want the plugin to request to github the latest release version and compare this with the current installed version on the server? And maybe print in the server log that a new version is available? |
@WoutProvost I think so. I tried to do this, but I couldn't. |
This website shows the latest releases of a given repo of a given username. The JSON output of this repo can be seen here (/repos/ziggi/FCNPC/releases get converted to /repositories/49101449/releases). The javascript code this website uses, can be found here. Second example: here. As for the c++ part, I have unfortunately not yet (still learning) mastered this language to know how to send a HTTP request or how to convert JSON to a c++ object, but StackOverflow or Google should provide an answer for that. |
@WoutProvost I know about it, but my problem in authorization. I will try again a bit later. |
Hmmm when trying to send a HTTP GET request to api.github.com it will fail (even without the https:// prefix), probably because of SSL. I have created a thread in the Scripting Help forums, but have not received an answer. |
@WoutProvost I think it is due to authentication. |
I really don't get why that should be a problem, since it is a public repository and a simple GET api call doesn't require authentication. Why does my browser respond with the correct HTTP Code, even when I'm signed out in GitHub? Is it because my browser is a recognised application? It really blows my mind why it will not just return HTTP 200 in the server. |
How about adding mechanism that will check latest releases and tell us if we are using outdated version. Its a simple thing but i just spent like 2h debugging and testing shit just to find the problem and then realize there is a new version that fixes bloody damage system...
The text was updated successfully, but these errors were encountered: