Package: github-backup
Version: 1.20130622
Severity: wishlist

The github API rate limit is 60 by default, which is very easy to hit
when running github-backup.

https://developer.github.com/v3/#rate-limiting

It would be great if github-backup could wait until the UNIX timestamp
from the X-RateLimit-Reset HTTP header when the X-RateLimit-Remaining
HTTP header reaches zero.

It would be great if I could specify some login credentials for Basic
Authentication or OAuth.

I can't tell if github-backup is doing this already but it would be
great if github-backup could use the Last-Modified, ETag,
If-Modified-Since and If-None-Match HTTP headers to only incur an API
rate limit penalty when there has been an update to the data:

https://developer.github.com/v3/#conditional-requests

With these in place I would never get any error mails from cron or
errors from mr backup and would not have to repeat github-backup
commands run interactively.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages github-backup depends on:
ii  git       1:1.8.4~rc3-1
ii  libc6     2.17-92+b1
ii  libffi6   3.0.13-4
ii  libgmp10  2:5.1.2+dfsg-2
ii  libicu48  4.8.1.1-13
ii  zlib1g    1:1.2.8.dfsg-1

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to