Leo Lamprecht

What's your OS? Not able to reproduce this on macOS Sierra 😊

Weeks are in https://github.com/zeit/ms/pull/55

Fixed in https://github.com/zeit/ms/pull/55

@mrkishi The pull request was closed

Check the `INTERVAL` env variable [here](https://github.com/zeit/hazel#options). What we can do is throw an error if people chose a lower interval than 1m or 2m (60 reqs per hour are allowed).

@zeke Correct. All unauthenticated. That's what makes Hazel so fast and powerful: It only abstracts the necessary. If you need server-side caching / private repos, there's Nuts... 😊

> I see. So hazel will only make a request to the GitHub API every `INTERVAL` minute(s), even though apps will be asking hazel for that info much more frequently....

The reason why we have chosen not to go with webhooks (like Nuts, for example) is that they simply don't scale that well: Assuming that you have 10 instances of...

Talking about [Now](https://zeit.co/now)'s way of scaling deployments, instances are completely separated from each other and therefore not able to determine whether or not other ones exist, where they exist and...

Actually we only need to run [this](https://github.com/zeit/hazel/blob/f2097713220933ff1a3de01f5ada781f295dc54a/lib/index.js#L14) when a certain path (let's say `/refresh`) is accessed. In addition, we need a new environment variable for a secret to compare with...