Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add script to reset individual instances

Open
#199 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker-compose

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.

Description

enhancement

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
Dominant language
PHP
Stars
190
Forks
103
Avg merge
4h 36m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/nextcloud-docker-dev

All issues in nextcloud/nextcloud-docker-dev

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.