fix(docs): list config.php keys to review when migrating servers#14852
Open
skjnldsv wants to merge 1 commit into
Open
fix(docs): list config.php keys to review when migrating servers#14852skjnldsv wants to merge 1 commit into
skjnldsv wants to merge 1 commit into
Conversation
skjnldsv
force-pushed
the
fix/migration-config-keys-review
branch
from
37ebb39 to
7dbe9f7
Compare
skjnldsv
requested review from
ChristophWurst,
artonge,
miaulalala,
nickvergessen and
provokateurin
Contributor
📖 Documentation Preview📄 2 changed documentation pagesLast updated: Fri, 15 May 2026 07:25:02 GMT |
Member
|
Changing data directory is not supported and should be avoided at any cost. |
Member
Author
We indeed have a dedicated section about this. https://docs.nextcloud.com/server/stable/admin_manual/issues/general_troubleshooting.html#troubleshooting-data-directory |
Member
Author
|
Done @nickvergessen |
Member
Author
|
Updated screenshot too |
susnux
reviewed
May 14, 2026
skjnldsv
force-pushed
the
fix/migration-config-keys-review
branch
from
e005493 to
750b122
Compare
skjnldsv
force-pushed
the
fix/migration-config-keys-review
branch
from
750b122 to
5482718
Compare
After copying config.php to a new machine, server-specific values (datadirectory, DB credentials, trusted_domains, etc.) silently stay wrong and cause startup errors or data corruption. The docs only said "adapt the paths" without being specific. Add an explicit important admonition listing every key that must be reviewed and updated before starting Nextcloud on the new server. Fixes #12919 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com> Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
skjnldsv
force-pushed
the
fix/migration-config-keys-review
branch
from
5482718 to
8fcb323
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
☑️ Resolves
What changed and why
The migration guide told users to copy
config/config.phpto the new server and only said "if you change any paths, adapt them in config.php". That is not enough — several keys are server-specific and will silently be wrong after a copy, causing startup errors or data corruption:datadirectory— path should not change (only on specific very rare cases)dbhost/dbname/dbuser/dbpassword— new DB instance = new credentialstrusted_domains— must include the new hostnameoverwrite.cli.url— must reflect the new URLmemcache.*/redisconnection params — cache host may differlogfile— log path may differAdded an
importantadmonition in step 4 (the file-copy step) that explicitly lists each of these keys and explains the consequence of leaving them stale.🖼️ Screenshots
codespellor similar and addressed any spelling issues