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

WakaTime support #1

Open
ErikBjare opened this issue Apr 14, 2016 · 2 comments
Open

WakaTime support #1

ErikBjare opened this issue Apr 14, 2016 · 2 comments

Comments

@ErikBjare
Copy link
Member

WakaTime has a settings file that enables setting a api_url and api_key. This can be used to effectively route all WakaTime requests directly to another entity (probably for debugging purposes). There is even an example config file called paranoid.cfg used in testing.

It would be nice to have a way to receive the heartbeats that WakaTime sends out so we can collect the data.

Now, to the matter on how that would be done in a nice way. Bundling it into the actwa-server core seems nasty to me, but creating plugins that are initialized with a reference to the flask app object and then set up the routes on it's own shouldn't be too involved. For prototyping it might be best to just bundle it into actwa-server directly (but keep it in it's own file so it will be easy to refactor into a seperate package and repo later).

The API is documented here: https://wakatime.com/developers/

@ErikBjare
Copy link
Member Author

A more pragmatic solution might be to write an importer tool.

@ErikBjare
Copy link
Member Author

ErikBjare commented Nov 16, 2016

An option to using the Wakatime API:

Wakatime stores a file ~/.wakatime.db which contains a SQLite store with not-yet sent heartbeats. Maybe disable sending of them via ~/.wakatime.cfg and hopefully they'll end up there for good.

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

No branches or pull requests

1 participant