-
Notifications
You must be signed in to change notification settings - Fork 2.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
Suggestion: Disable (Web-)Updater by default. #41149
Comments
Leaving my two cents: While the updater is being named "App" all over the place, it significantly differs from the "classical" apps in the marketplace which can be installed/uninstalled at will. It is reasonable to disable the feature in the standard config due to its potential risks. However, a more elegant option might be to extract the functionality into a "real" app. This way, the feature can be disabled by default if the app is just not installed, but everyone could choose to use it if they want to. This might also tackle the issue of the correlated release with the core as described in the issue, as the updater itself would be updateable. |
Does this config also activate/deactivate calling the updater via the command line or only from the GUI? (Because using it from the command line is just as error prone.) |
Looks like there have been some considerations in the past: owncloud/updater#409
The same issue from above has also:
but without giving much reasons why
TBH i don't know, i'm not familiar with the innter workings of ownCloud and just using it But i think the command line is not that easy to start then a one-click button in the GUI so if only the GUI would be disabled by default it would be a big step forward. |
I agree with that. Regarding the old discussion most of these people seem to still be in the OC team, so it might be good to get their opinions, but let's wait for this issue to gain traction first. |
Suggestion: Make updater work by default |
As this hasn't happen since many years i wouldn't put high hopes on that :-) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
Bump |
It seems the Updater shipped within ownCloud core releases has a long track of being the root cause for update failures (like recently seen in owncloud/updater#729 (#41057), owncloud/updater#726 or #41160 but also in other GitHub / Forum user reports, and also due to the lack of features like owncloud/updater#356 to check for a PHP compatibility before starting the update).
Another issue originating from using the Updater is the following as mentioned in owncloud/updater#713 (comment):
Furthermore even the documentation at Upgrade Options is not recommending the Updater and most importantly also includes the following:
As (quite commonly happening) a user, especially the less technical firm ones usually won't read the documentation and just click on "Update" in the Web GUI which is leading rather sooner then later to a bad update experience (i never had any so far but not using the Updater at all).
In addition the Updater is also not enabled in the Enterprise edition according to Upgrading ownCloud with the Updater App:
And finally the same page has also a warning / caution (which is usually also not really read):
With all that in mind wouldn't it make sense to disable the Updater by default in the Community Edition and tell the users that they need to enable and use it on their own risk?
'upgrade.disable-web' => true,
from e.g. theconfig.sample.php
The text was updated successfully, but these errors were encountered: