unclear installation depedency on <data> dirs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Steps to Reproduce
- Follow the installation steps in a fresh environment e.g. a virtual machine
Expected Behaviour
The required local dirs should be either automatically created (add to an init script?) or mentioned as prerequisites:
Maciejs-MacBook-Pro:overleaf-toolkit maciejskorski$ ls data
git-bridge mongo overleaf redis
Observed Behaviour
With no data dirs, e.g. in a fresh environment, docker compose fails to start a container.
Context
Technical Info
Analysis
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 following the installation steps in a fresh environment and inspect the Docker Compose configuration that fails when data directories are absent. Check whether the toolkit has an initialization script or documented prerequisites; done means a fresh setup creates or clearly requests the required directories and docker compose starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100