Maybe document subfolder based access (example)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
There's a distinction between a subfolder installation of Nextcloud (i.e. somewhere under the docroot) and merely making Nextcloud reachable via a subfolder style URL (https://domain.tld/nextcloud). The former is not something relevant to this image, while the latter is a config matter (including reverse proxy integration)
There's probably an opportunity to improve upstream documentation and/or our docs & examples here at the Docker level.
I mention this so that maybe we can finally close out the following issues:
- #401
- #1919
- #2187
- #1047
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
Begin with issues #401, #1919, #2187, and #1047, then review the project's existing Docker documentation and examples for subfolder URL configuration and reverse-proxy integration. Done means the distinction between installation location and subfolder access is documented, with the relevant Docker-level guidance or examples updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100