Affected Area
Running the install & upgrade scripts, as well as simply starting the server trigger calls to the GitHub API to check versions. Unauthenticated, we're only allowed 60/hour, which simply isn't enough if you're trying to install the tool, and facing issues along the way -- it doesn't take many failed install attempts before you're blocked out.
It's not a breaking issue, so have labelled as an enhancement for now.
Requested Feature
A few possible routes we can take:
- First point of call would be to look at optimising my installHelpers code, as I'm sure this calls the GitHub API more than it needs to...
- Authenticate somehow (would be an annoying barrier to people before they've even installed the thing)
- Revert back to git (we'd lose the handy release metadata we get from the github API)
- Provide some kind of fallback in the event of a lockout (perhaps we just skip the version checks)
Affected Area
Running the install & upgrade scripts, as well as simply starting the server trigger calls to the GitHub API to check versions. Unauthenticated, we're only allowed 60/hour, which simply isn't enough if you're trying to install the tool, and facing issues along the way -- it doesn't take many failed install attempts before you're blocked out.
It's not a breaking issue, so have labelled as an enhancement for now.
Requested Feature
A few possible routes we can take: