-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fetch app updates prior to starting Nextcloud upgrade #580
Comments
cc @Altahrim |
The Updater itself technically doesn't handle upgrading of the apps, have db access, nor have access to any of our usual APIs. We should probably handle all this prior to even invoking Updater let alone We do have a convenient spot before Updater: the
Not quite following the context for this one. Are you talking about where to drop the Archive files for the new pre-downloaded apps? |
Yes, that is true, but it is already download the server code, so downloading relevant apps is not so far off either. The issue with loading them before invoking the updater has the issue that the apps have to be put somewhere, and not replace current apps (they might not be compatible). There would be ways around this too, though.
For the
Yes, they have to be put in place after replacing the nextcloud server code. |
Related: nextcloud/server#33561 |
To combat issues like nextcloud/server#47602 we should also fetch necessary app archives around downloading the nextcloud release.
A brainstorming with @nickvergessen brought up these ideas:
Allow to specify apps that shall be ignored per parameterReport, but otherwise ignore apps that are not available on appstore--force
is specified.The text was updated successfully, but these errors were encountered: