nextcloud / nextcloud/nextcloud-docker-dev
Add script to reset individual instances
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
Currently the only way to reset an instance is to call docker compose down -v which is quite bad as it will remove all instances and their data.
Ideally we'd have a small helper script which would:
- Remove the manually picked container and its volumes
- Drop the s3 bucket if used
- Drop the database only for the picked container depending on which db backend is used
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 by tracing how this development environment defines instances, containers, volumes, S3 buckets, and database backends around the docker compose setup. Confirm how a manually selected container maps to its associated resources. Done means a helper can reset only the selected instance, including its volumes and applicable S3 bucket and database, without affecting other instances or their data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100