Opcache revalidation impact on config changes
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Since we have the cache revalidation time set to every 60 seconds, on-disk config changes don't take effect immediately.
We should probably document that somewhere[^imo]. :-)
Refs:
https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html#revalidation
[^imo]: That or set it back to the default (2s).
Contributor guide
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 with Dockerfile-alpine.template at line 97 and the linked server tuning documentation on revalidation. Identify the appropriate project documentation location, explain that the image's 60-second revalidation delays on-disk config changes, and consider documenting the alternative default setting; done means the behavior and setting are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100