Example for custom apps directories does not work correctly #739
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This configuration example does not work because apps shipped with Nextcloud can not be updated. Changing the app directory order fixed that.
julijane
changed the title
|
From the same doc: To ensure that the default /apps/ folder only contains apps shipped with Nextcloud, follow this example to setup an /apps2/ folder which will be used to store all other apps. So I'm asking myself if this is not a wanted behavior that you can only update non-core apps. Why do you want a write protection on your apps folder in the first place? related: nextcloud/server#8929 |
|
@julijane this was an issue in our code, this has been fixed now :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This configuration example does not work because apps shipped with Nextcloud can
not be updated.
There is a current example. Nextcloud 13.0.1 ships with files_pdfviewer 1.2.0, but an update to 1.2.1 is available. However when using a configuration as shown in the example (and as similarly used in nextcloud/docker) updating does not work. The update is downloaded and installed into the second "writable" app directory, however Nextcloud will still load the old version as shipped and continue to complain about an update being available.
Changing the order so that the "writable" folder comes first fixed this. Updates are put there and Nextcloud uses them. This is arguably a bug in the server but I am not sure about that.
See also nextcloud/docker#308