Console Compatibility Notes

Differences between SILO Console and the upstream MinIO Console

SILO Console is Silo’s build of the MinIO Console. This page records where the two are interchangeable and where they differ.

pgsty/silo-console continues the upstream minio/console history from its final commit, feff71e4 (2026-04-16); the rebrand begins at 50797deb (2026-08-04). The upstream repository is no longer published — github.com/minio/console now returns 404, where minio/mc was merely archived — so the source lineage survives only in this fork. The Go module path still resolves, because the module proxy continues to serve the versions it already cached. Fork releases to date: v2.0.0, v2.1.0, v2.1.1, v2.2.0, and v2.2.1.

Principles

The fork follows the same rule as the rest of Silo: the shipped artifact and its channels are renamed; the interfaces other software depends on are not.

Renamed — the artifact on disk (silo-console), the product identity in the interface and in --version, the distribution channels, and the signing keys.
Unchanged — the Go module path github.com/minio/console, every CONSOLE_* environment variable (including CONSOLE_MINIO_SERVER and CONSOLE_MINIO_REGION), the REST API shapes the web application calls, and the packaging identifiers minio-console.service, console-user, and /etc/default/console, so an in-place package upgrade keeps working.
Severed — automatic self-update, telemetry, analytics, beacons, external scripts and fonts, and call-home. A release catalog is contacted only when one is explicitly configured, through SILO_RELEASE_SERVICE_HOST with RELEASE_SERVICE_HOST retained as a fallback.
Preserved — upstream copyright and the AGPL-3.0 license. Runtime output credits both MinIO, Inc. and PGSTY.

Note

SILO Console is not a generic S3 browser. Its administrative features need the MinIO-compatible administration APIs that Silo implements in addition to the S3 API.

What changed

1. The full administration console is retained

This is the largest functional difference, and it runs opposite to the usual direction of a fork. Upstream reduced its community console to an object browser. SILO Console keeps the complete administrative interface: dashboards, health, logs, diagnostics, and speed tests; bucket, object, lifecycle, replication, notification, and tier management; users, groups, service accounts, policies, identity providers, and KMS setup; and server configuration.

2. The dashboard targets Metrics V3

Dashboard widgets query the MinIO Metrics V3 catalog, the metric set current deployments actually scrape, with guards for its zero-value and per-node export semantics so a panel distinguishes a real zero from missing data. The mapping is recorded in docs/metrics-v3.md.

3. A smaller, quieter payload

The embedded frontend went from roughly 10 MB to under 3 MB, rebuilt reproducibly byte for byte and enforced by a release gate. There is no telemetry of any kind, and no external network dependency in the page itself.

4. Bilingual interface

The interface, help content, and documentation links are available in English and Chinese behind a per-page toggle, with no added runtime dependencies.

5. For developers: the module graph

The Go module path stays github.com/minio/console, and Console’s own require directives stay on resolvable upstream versions — notably github.com/minio/pkg/v3 v3.6.1. Those requirements are part of Console’s public module graph, and Go selects the maximum requirement across the whole graph, so raising them would push every embedding server’s module graph up with them.

The maintained Silo implementations are selected by replace directives instead:

replace (
	github.com/minio/mc          => github.com/pgsty/mc ...
	github.com/minio/minio-go/v7 => github.com/pgsty/silo-go/v7 ...
	github.com/minio/pkg/v3      => github.com/pgsty/silo-pkg/v3 ...
)

Two consequences follow, and both bite in practice:

Replacements are not inherited. Go ignores replace directives declared by a dependency module. A server that embeds Console source has to repeat these selections in its own go.mod, or it will silently build Console against the upstream packages.
Adopt them as one set. The CLI and the shared package are coupled: pgsty/mc compiles against the Silo package’s strict policy API. A build that keeps the CLI replacement must keep the shared-package replacement too. Go will resolve a partial override that pairs one project’s CLI with the other’s shared package, but Console neither supports nor tests it.

Console’s own source avoids fork-only APIs — it applies its strict policy-write checks locally rather than importing them — and a CI job proves it by dropping all three replacements and building, vetting, testing, and cross-compiling against the pure upstream graph. That is a build-compatibility guarantee, not a claim that the upstream and Silo packages behave identically at runtime.

Migration

An existing MinIO Console deployment upgrades in place. The service unit, service account, and configuration file keep their names, and every CONSOLE_* variable is read unchanged, so the usual path is to install the silo-console package over the old one and restart.

Two behaviors change on first start and are worth expecting:

silo-console will not update itself. Roll out new versions through packages, images, or your orchestrator.
Any workflow that relied on the console reaching MinIO-operated services — the update feed, licensing, or telemetry — no longer has anything to reach.