caddyserver / caddyserver/cache-handler
Design/spec discussion
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 393
- Forks
- 28
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Description
Currently, this handler works in the most basic sense, but it has a lot of potential and needs some TLC before being truly production-ready. Right now, it's a great foundation to build from.
Since this module was recently spliced out of Caddy's standard modules before the RC1 tag, previous discussions can be found here:
- https://github.com/caddyserver/caddy/issues/10
- https://github.com/caddyserver/caddy/issues/1489
- https://github.com/caddyserver/caddy/pull/1759
- https://github.com/caddyserver/caddy/issues/2820
Plus the third-party v1 implementation of a cache middleware: https://github.com/nicolasazrak/caddy-cache
With the context from those previous discussions in mind, where should we take this project? Who will take the lead in developing it?
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
Start by reading the linked Caddy discussions, pull request 1759, and the third-party v1 cache middleware referenced in the issue. The issue does not name implementation files or tests; done would require an agreed direction for the handler and a maintainer or contributor taking ownership.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100