nextcloud / nextcloud/nextcloud-docker-dev
New stable versions aren't created without a reinstall
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
Following the standard documentation and creating a worktree results in a setup where "stable31.local" is not accessible.
There don't seem to be any differences from the logs produced by turning on stable30, so there is no logged error I can see.
How to reproduce:
- Setup
nextcloud-docker-dev - Have a new stable version come out
- Clone the new stable version and set up a worktree
- Run
docker compose up stable[x] stable[x].localis not accessible on localhost. It only becomes accessible by doing a complete reinstall withbootstrap.sh
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 bootstrap.sh and the docker-compose setup described in the reproduction steps, then compare the provided log.txt with the stable30 logs. Verify the new stable worktree can be started with docker compose up stable[x] and that stable[x].local is accessible without a complete reinstall.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100