Support custom `datadirectory` (i.e. not called `data`) located in Nextcloud installation folder
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
Updating NC 14.0.3 to .4 failed at "Check for expected files":
"The following extra files have been found:
o [custom pathname for file repository]
o .well-known"
Update does not continue.
-
These are not "files" but directories. Please be exact.
-
Custom pathname for file repository has been defined, Update has to respect this.
-
".well know" is a required directory for automatic verification to get a Let´s Encrypt SSL certificate by a widespread Plesk Panel extension. Update should tolerate this. -
These are two conditions which should not break the update process. Using a software to keep the personal data in own hands should per se not deny the user´s wish.
-
Update routine of NC 14.0.03 seems to be unable to continue. May be a patch file is required.
-
This issue seems to be very, very old, see https://github.com/nextcloud/updater/issues/92
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 by reproducing the update failure described in the issue and inspect the updater's check for expected files. Done means an installation with a custom datadirectory and the .well-known directory can pass the update check, with directories reported accurately rather than as files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100