Document Subpath-based Installation (e.g. https://domain.org/dataverse)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Dataverse installation currently only supports URLs without a path (e.g. https://domain.org). Hence, it is mandatory to use a subdomain (e.g. https://dataverse.domain.org) or to use 3rd party tools to translate URL addressed on-the-fly (beyond URL rewriting). Would you consider supporting custom paths natively? Adding a baseURL parameter, or extending siteURL parameter to support path besides domain name and port might be a solution.
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
The issue names siteURL and a possible baseURL parameter but does not identify files, tests, or an entry point. Start by locating how siteURL is parsed and used to build installation URLs, then define and test the expected behavior for a path such as /dataverse across the affected links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100