pgsty/mc repository overview

⁠mcli

A conservatively maintained MinIO Client fork Versioned client builds and compatible administration tooling for Silo, Pigsty, and S3-compatible object storage.

Website⁠ · Documentation⁠ · Download⁠ · Blog⁠ · Releases⁠ · Security⁠ · 中文⁠

Important

pgsty/mc is an independent, community-maintained fork of the open-source MinIO Client⁠, published by Pigsty⁠. It is not affiliated with, endorsed by, or sponsored by MinIO, Inc. “MinIO” is used only to identify the upstream project and compatibility lineage.

⁠Overview

pgsty/mc maintains one downstream release line based on the archived upstream MinIO Client branch at 77f82e18⁠. It provides maintained client builds after the upstream repository was archived.

This fork exists so Silo⁠ and Pigsty deployments have a compatible CLI that can be built, patched, tested, and released through the same maintained supply chain. It also remains a general-purpose client for filesystems and Amazon S3-compatible object stores.

The official project portal is silo.pgsty.com⁠. It brings the client reference, downloads, release and security notes, and project legal information together. English is served at the site root; Chinese is available under /zh/⁠.

⁠Find the Right Resource

⁠Maintenance Policy

The active master release line covers:

• build, toolchain, and dependency maintenance;
• applicable security fixes and sensitive-output hardening;
• focused fixes for reproducible defects and Silo interoperability;
• versioned archives, Linux packages, checksums, and multi-architecture images;
• release automation, documentation, and Pigsty integration.

Changes are kept narrow and tested where practical. Maintenance is best effort; no response, remediation, or release schedule is guaranteed.

⁠Out of scope

• a separate client roadmap, new object-storage protocol, or speculative commands;
• broad rewrites or changes that materially expand the downstream delta;
• historical releases or multiple support branches;
• commercial support, SLAs, 24×7 coverage, or SUBNET services;
• guaranteed compatibility with every S3 implementation or future proprietary MinIO API.

⁠Compatibility

This fork aims to preserve:

• the github.com/minio/mc module path, ~/.mc configuration, and familiar command behavior;
• S3 Signature V2/V4 access and common MinIO/Silo administration workflows;
• RELEASE.YYYY-MM-DDTHH-MM-SSZ tags and the mc container entrypoint;
• the mc name for source builds, while standalone archives and Linux packages use mcli; the Silo image provides both names.

The mc update command is intentionally disabled. Upgrade through the Pigsty package repository⁠ or GitHub Releases⁠.

Compatibility is a goal, not a guarantee. Server-specific administration commands may vary across versions. Pin releases, review the release notes, keep a rollback path, and test the client against the target service before production use.

⁠Downloads and Release Artifacts

Use Download & Install⁠ to choose a client installation method. GitHub Releases remains the source for versioned archives, packages, checksums, and source archives.

⁠Quick Start

Standalone archives and Linux packages expose the command as mcli:

mcli alias set local http://127.0.0.1:9000 ACCESS_KEY SECRET_KEY
mcli mb local/demo
mcli cp README.md local/demo/
mcli ls local/demo

The container retains the familiar mc entrypoint:

docker run --rm pgsty/mc:latest --version
docker run --rm pgsty/mc:latest ls play

Warning

For production, pin a release instead of latest, verify checksums, use TLS and least-privilege credentials, and test destructive commands against non-production data first.

Build from source:

git clone https://github.com/pgsty/mc.git
cd mc
make build
./mc --version

⁠Common Commands

Run mcli --help, mcli <command> --help, or consult the client reference⁠ for the complete command set.

⁠Contributing

Useful contributions include security and dependency updates, reproducible bug fixes, interoperability tests, release automation, packaging, and documentation.

Issues and pull requests should include the affected client and server versions, reproduction steps, impact, expected behavior, tests, and compatibility notes. Discuss large changes in an issue first.

⁠Background

The upstream minio/mc⁠ repository was archived after its final 2025 development line. Pigsty maintains this fork because Silo needs a reproducible companion client release channel rather than depending on an archived upstream project.

The broader upstream changes, alternatives considered, and early fork maintenance record are documented below:

⁠License, Attribution, and Trademark

The client source is distributed under the GNU Affero General Public License v3.0 or later⁠. This fork derives from minio/mc⁠: NOTICE⁠ retains the upstream product notice, CREDITS⁠ records licenses and notices for included third-party components, and the Git history records downstream modifications.

MinIO is a trademark of MinIO, Inc. The name is used here only to identify the upstream project and compatibility lineage. Pigsty, Silo, pgsty/mc, and mcli are independent community efforts and are not affiliated with, endorsed by, or sponsored by MinIO, Inc.

The portal separately publishes the project license summary⁠, documentation attribution⁠, and trademark notice⁠.