https://github.com/karlicoss/rescuexport

Export/access your Rescuetime data
https://github.com/karlicoss/rescuexport

backup data-liberation export rescuetime

Last synced: about 2 months ago
JSON representation

Export/access your Rescuetime data

• Host: GitHub
• URL: https://github.com/karlicoss/rescuexport
• Owner: karlicoss
• License: mit
• Created: 2019-11-28T10:35:08.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2023-10-25T01:17:06.000Z (about 1 year ago)
• Last Synced: 2024-05-30T01:15:23.691Z (7 months ago)
• Topics: backup, data-liberation, export, rescuetime
• Language: Python
• Homepage:
• Size: 37.1 KB
• Stars: 11
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.org
  • License: LICENSE

Awesome Lists containing this project

README

        
#+begin_src python :dir src :results drawer :exports results

import rescuexport.export as E

return E.make_parser().prog

#+end_src

#+RESULTS:

:results:

Tool to export your personal Rescuetime data

:end:

# TODO document this??

# Note that this script only backs up last 30 days of data.

# If you need to export *all* of your Resquetime data, a bit of extra work is required (pretty straightforward though!)

* Setting up

The easiest is to run =pip3 install --user git+https://github.com/karlicoss/rescuexport=.

Alternatively, you can =git clone --recursive= and use =pip3 install --editable=

* Exporting

#+begin_src python :dir src :results drawer :exports results

import rescuexport.export as E

return E.make_parser().epilog

#+end_src

#+RESULTS:

:results:

Usage:

*Recommended*: create =secrets.py= keeping your api parameters, e.g.:

: key = "KEY"

After that, use:

: ./export.py --secrets /path/to/secrets.py

That way you type less and have control over where you keep your plaintext secrets.

*Alternatively*, you can pass parameters directly, e.g.

: ./export.py --key 

However, this is verbose and prone to leaking your keys/tokens/passwords in shell history.

I *highly* recommend checking exported files at least once just to make sure they contain everything you expect from your export. If not, please feel free to ask or raise an issue!

:end:

# FIXME ./export.py is no longer correct way...

# eh, gonna need to somehow pass the package name into export_helper??