simonw / simonw/datasette-auth-github
Option to define allowed GitHub user IDs in an external file via URL
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 46
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Idea for an alternative mechanism: allow users to define a JSON file of GitHub user IDs that are allowed access. They can host this at a separate URL - e.g. in a gist. Datasette hits that URL and caches it for a few seconds between hits to figure out who is allowed access.
Originally posted by @simonw in https://github.com/simonw/datasette-auth-github/issues/67#issuecomment-766276016
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing GitHub access-control configuration and authentication flow, then determine how a URL-hosted JSON allowlist and short-lived caching should fit there. Done means users can configure the external allowlist and access decisions reflect its contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100