No support for external nginx instance
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
It's great that there is a well built mechanism for running a stand-alone instance of sharelatex, but for those wanting to spin it up in a docker container and use an existing nginx reverse-proxy setup (such as one would want to do on a home server), this is a real pain in the neck. What should be a 5 minute job is basically impossible.
Contributor guide
No contributing guide indexed for this repository
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 by tracing how the standalone instance launches its nginx reverse proxy and how the Docker container is configured. Define the configuration and startup changes needed to use an existing external nginx while keeping the container deployment working. Done means a home-server user can follow the setup without running the bundled nginx instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100