nextcloud / nextcloud/nextcloud-docker-dev
Support for multiple virtual hosts per service in nginx-proxy
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
Currently the VIRTUAL_HOST environment variable is used by Nextcloud containers to derive an identifier for the instance among other things. This puts some limitations on how nginx-proxy can be used with regard to multiple virtual hosts.
I have a use case where I want to add an external reverse proxy on the web while also keeping the local setup intact. You can find a PoC here https://github.com/smesterheide/nextcloud-docker-dev/tree/app/vo-federation.
If there is interest in this I can create a PR where we disentangle the VIRTUAL_HOST environment variable.
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 repository's docker-compose setup, the VIRTUAL_HOST usage, and the linked nginx-proxy documentation on multiple hosts. Compare the linked app/vo-federation PoC and define how separate host configuration should preserve the local setup; done means the intended multi-host use case works without relying on one VIRTUAL_HOST value for unrelated identification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, nginx
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100