Skip to content

client_id and client_secret of GitHubRepoProvider per server #3872

Description

@rgaiacs

It was reported to me that mybinder.org was returning the code 429 (too many requests).

Image

Angus pointed to me that this happens when repoproviders from BinderHub reaches GitHub REST API limit.

At the moment, all servers in the federation uses the same client_id and client_secret for GitHubRepoProvider. Should we change to require every server to use its own client_id and client_secret? This will effectively increase the capacity and resilience of the servers in the federation.

@minrk do you think this is something feasible for BIDS?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions