nextcloud / nextcloud/nextcloudpi

Clarifying menus and script naming in NextcloudPi

Open
#1,581 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
2.9k
Forks
318
PR merge metrics
No merged PRs in 30d

Description

Description
Cleaning up some of the menus and naming. Not a huge deal, but spit and polish

nc-admin and nc-password are confusingly similar.
nc-update does not mention it is for NextcloudPi tooling, while nc-update-nextcloud is for Nextcloud.
Set Trusted Domains is in a different menu than other networking options like Trusted Proxies.
I will add to this as I find more things I'd like to clarify.

Related to #1566

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

Start by locating the nc-admin, nc-password, nc-update, and nc-update-nextcloud scripts and the menu entries for Set Trusted Domains and Trusted Proxies. Review how their names and menu placement currently distinguish NextcloudPi tooling from Nextcloud operations. Done means the names are clear and related networking options are grouped consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.