[Feature Request] Support deployment behind a path
Nobody has claimed this yet.
- Dominant language
- Elm
- Stars
- 1.3k
- Forks
- 72
- Avg merge
- 21h 30m
- Merged PRs (30d)
- 1
Description
It is common that services like Sharry are hosted on a local server, and accessed through a reverse-proxy publicly available.
As I have several services (and cannot have sub-domains), I address each of them through a sub-path in the url, like :
http://public-name/service1/
http://public-name/service2/
etc
As it is mentioned in the config file, this is not currently supported since the app will redirect navigator to http://public-ip/app, breaking the sub-path reversed proxy :
# Note: Currently deploying behind a path is not supported. The URL
# should not end in a slash.
This ticket is for adding support of deployment in sub-path url.
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
Start with the deployment URL configuration referenced in the issue and trace how the application builds redirects when hosted behind a reverse proxy. Done means the application works under a configurable sub-path without redirecting to the root path; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elm
- Domain
- infrastructure, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100