nextcloud / nextcloud/server

Extending the status command if S3 is the primary storage.

Open
#49,465 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: object storage
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
We want to extend the status.php functionality to get more information about the S3 (MinIO) storage. Currently, we are faced with the issue of the impossibility of getting a proper reply from MinIO to Nextcloud.
Describe the solution you'd like
So, we are working on it. Would having the following data in the status.php be a good idea?

  • Primary object store is not configured;

  • Primary object store is not configured as S3;

  • Checked CRUD (accessibility) for the current bucket;

  • Occupied space in a bucket;

  • An issue with the S3 service with an explanation.

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.

Research direction

Start with the existing status.php functionality and trace how primary S3 or MinIO storage is represented. Define how the status output should report configuration, bucket CRUD accessibility, occupied space, and service errors, then verify each requested condition against a configured current bucket.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, php
Domain
backend, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.