Document the default storage backend to the README
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with README.md at lines 6-9, using the linked revision from the issue. Confirm which storage backend “one storage” refers to, then update that README section so the default is named directly; done means the documentation is unambiguous without following the link.
Written by the indexing model from the issue text.
Description
The link does not reveal which one the one storage is. The README would be improved by documenting this directly.
- Dominant language
- Go
- Stars
- 394
- Forks
- 28
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from caddyserver/cache-handler
-
Admin API purge/invalidation still panics with nil pointer on v0.16.0 (same root cause as #140)Open
Difficulty 3/5 1-2 days Newbie friendliness 76/100
caddyserver/cache-handler#143 · 2 comments ·
-
Can not flush cacheOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
caddyserver/cache-handler#140 · 4 comments · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
caddyserver/cache-handler#139 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
caddyserver/cache-handler#137 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
caddyserver/cache-handler#136 · 4 comments ·
All issues in caddyserver/cache-handler
Similar issues
-
feedback laptop
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Validator client startup retry loop ignores context cancellation until the reconnect backoff expiresOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OffchainLabs/prysm#17596 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
status: ready for dev
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
hyperledger-labs/fabric-smart-client#2004 ·
Maintainers usually reply within 1 day