mcli

The command-line for Silo — a MinIO Client fork maintained by PIGSTY

Website · Documentation · Download · Release Notes · Compatibility · Security · 中文

pgsty/mc maintains one downstream release line based on the final upstream MinIO Client commit, 77f82e18. After the upstream repository was archived, this fork keeps the client built, patched, tested, and released through the same maintained supply chain as the Silo object storage server, while remaining a general-purpose client for filesystems and Amazon S3-compatible object stores.

The fork follows one rule: the shipped artifact and its distribution channels are renamed; the tool you use is not. Standalone archives and Linux packages ship the binary as mcli, while commands, flags, configuration, and wire behavior stay unchanged from upstream. The complete, versioned list of differences is maintained in the compatibility notes.

The official project portal is silo.pgsty.com. It brings the command reference, downloads, release and security notes, and project legal information together.

The active main 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.

• 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.

The client is maintained together with the Silo server under one release process: DCO-signed commits, reviewed pull requests, and versioned RELEASE.YYYY-MM-DDTHH-MM-SSZ tags with checksummed artifacts. Each release is announced with a release note on the portal; security advisories follow the security policy. Upstream copyright, license, and third-party notices are preserved in LICENSE, NOTICE, and CREDITS.

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.

Connections to MinIO-operated services — the update feed, SUBNET, telemetry, and the pre-seeded play alias — are severed; affected commands remain for script compatibility and fail with a stable error. In particular, mc update 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 and compatibility notes, keep a rollback path, and test the client against the target service before production use.

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

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 alias ls

Build from source:

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

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

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.

There is no CLA: contributions are accepted inbound=outbound under the project license (AGPL-3.0-or-later) and contributors keep their copyright. Every commit must be signed off (git commit -s) per the Developer Certificate of Origin; see CONTRIBUTING.md.

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:

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.