-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add opcache validate/re-validate setupCheck (or warning in Updater) #45498
Comments
pseudo code (all wrapped behind a check that
I was originally leaning towards putting this in the This would allow those operators that adjust validation to not be permanently nagged by the warning in the general setupchecks... but still would allow us to later add in friendly and non-intrusive reminders in This approach has the benefit of:
|
Both AIO and the micro-services Docker images sets That's obviously more than the default of Need to decide how to handle that. The higher the number goes the higher the likelihood of people experiencing weird behavior when making config changes or upgrades. 🤔 |
Inform operator if restarting mod_php/fpm is more likely than not to be needed after triggering an Upgrade so people are less surprised when this happens and/or to remind people that adjust these values but then later forget. :)
Options:
updatenotification
app that gets displayed on the Updater screenOr:
Currently going to focus on clarifying in the documentation: nextcloud/documentation#11872
Related:
The text was updated successfully, but these errors were encountered: