nextcloud / nextcloud/nextcloudpi

ncp-web/wizard wishlist

Open
#622 22 comments 0 reactions 1 assignee View on GitHub

@nachoparker is already working on this.

Since Jan 20, 2021.

enhancement help wanted ncp-web wizard
Dominant language
Shell
Stars
2.9k
Forks
318
PR merge metrics
No merged PRs in 30d

Description

Wishlist of features / enhancements for ncp-web. This list complements #380, but these mostly don't need to wait until the backend changes.

ncp-web

  • a special view for nc-restore where you can see a list of available backups and click on one of them
  • a directory picker widget so you can select a folder by browsing the server, instead of typing the path. This would be useful for several apps, like nc-datadir, nc-database...
  • a way to upload files, such as a backup or a config file
  • ability to show/hide the sidebar with a swipe (mobile phone)
  • sanitize input in javascript. Probably after #380
  • replace translation engine for something more automatic (weblate or similar)
  • search based on (translated) text, not only ncp-app id
  • associate urls with sections, and be able to use history ( eg: nextcloudpi.local:4443/#nc-datadir)
  • a search box
  • file exists indication when there is a path in the text box
  • a python test in the test folder
  • "typed fields", so for instance passwords are hidden while typing, checkboxes, file paths...

wizard

  • the wizard needs a couple new things integrated: enable automatic NC updates and NCP updates, maybe activate UFW
  • rewarn before formatting that the contents of the drive will be lost
  • check for updates/update at beginning of wizard (like ncp-web)
  • disable fail2ban,dnsmasq if selecting "no external access"?
  • more DDNS clients
  • prefill text input boxes with past input
  • detect open ports, and only ask to use upnp if needed
  • detect nat loopback and only activate dnsmasq if necessary
  • new proposed design in https://github.com/nextcloud/nextcloudpi/issues/272
  • translations

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.