Support container_name modification
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Hi as far as I can tell there is no way to specify the container_name value without manually modifying the following compose file under lib/. I think that this would be a nice feature to include in config/overleaf.rc to allow for multiple toolkit or custom docker-compose.yml files of the main overleaf/overleaf to be deployed to the same docker daemon for testing purposes.
https://github.com/overleaf/toolkit/blob/e8b536cad7b89ccf6fb53d40f3a97c4a7fa8d32b/lib/docker-compose.base.yml#L8
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 with lib/docker-compose.base.yml at line 8 and inspect how config/overleaf.rc is used to generate or customize Compose files. Confirm how a configurable container_name should flow through the deployment, then verify that multiple toolkit or custom overleaf/overleaf deployments can run on the same Docker daemon without manual edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100