exercism / exercism/project-management
Add support for favicon links
Open
- Dominant language
- No language data
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Get the favicon URL for all `links.json` files.
- [ ] Store the link-mapping in redis?
- [ ] Put up a proxy between them (so we're not directly linking to links on other sites and leaking user's data)
I'm thinking 1+2 get triggered by a change to the links.json file, and a sporadic (weekly?) task to check the links are ok. Then if the proxy hits a link which returns a 404 at any point, we can also retrigger the job then.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.