nextcloud / nextcloud/docker

README Migrating Existing Installation Unclear Instructions

Open
#1,155 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. To develop bug docs
Dominant language
Shell
Stars
7.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

I was just following the README for migrating an existing installation to a Dockerized installation: https://github.com/nextcloud/docker#migrating-an-existing-installation

The steps are numbered in this order: 1, 2, 3, 4, 5, 3, 4, 4, 5. After I got to step 5 (the first one), which says to remove all lines pertaining to app_paths, it then proceeds to step "3" which says to keep the app_paths lines and set them a certain way. But wait, I just deleted them all!

I'm happy to submit a pull request, but first need some clarification on which approach to take. Basically, do we need to keep the app_paths and configure which ones are writable or read only? Or do we just remove those lines entirely and forget about it?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the README's “Migrating an existing installation” section and review the numbered steps around the app_paths instructions. Resolve the contradiction between removing app_paths lines and retaining or configuring them, then make the sequence and guidance consistent. Done means the migration steps are sequential and no longer give conflicting app_paths directions.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.