-
Notifications
You must be signed in to change notification settings - Fork 1
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
Wakapi support #37
Comments
I've looked at the API, but I think it lacks too many endpoints to have a functional app. Also there's no way to detect whether an endpoint it missing. |
btw, I wonder, would the app fully works for official wakatime if you just specify the wakatime official api url and api key? Is there any special benefits from verifying from a browser? |
I am trying to add support for it in #38, but the I have opened an issue on the repo: muety/wakapi#190 |
Once muety/wakapi#192 is fixed. Most of the features of the app should be working, apart from projects, commits, etc... |
Merged! There's stuff that's missing, but not too much. The other required endpoint would be the one for the user data, right now it'll display "anonymous user" instead When endpoints are added it should start working automatically without an app update needed. I'll be realising a new version probably tomorrow. |
I'm trying to connect to a local instance of wakapi running on localhost, accessible from my android at an IP like http://192.168.1.1:8080. |
wakapi is a Wakatime-compatible backend, it lacks some features of wakatime (such like leaderboards) but there are some basic APIs are implemented.
You can check Wakapi API at here
To have support for wakapi, I think at least it should show an option to specify the
api_url
andapi_key
on start at first. maybe disable some components when some API method is not available.The text was updated successfully, but these errors were encountered: