mirror of https://github.com/pgsty/minio.git synced 2026-08-10 08:13:28 +03:00

Files

T

Feng Ruohang fd2ca1c6d2 docs: rebrand the repository documentation, templates and dashboards

README, README_ZH, SECURITY, COMPLIANCE, CONTRIBUTING, NOTICE,
code_of_conduct, the vulnerability and PR-etiquette documents, the GitHub issue
and pull request templates, and the docs/ tree all present Silo as the product.
The Grafana dashboards under docs/metrics/prometheus/grafana/ have their panel
titles and descriptions rebranded while every minio_* query, label and
expression is left alone, so existing alerts and recording rules keep matching.

The distinction the review demanded is applied per hit rather than by
search-and-replace:

- Product and command text becomes Silo and silo: install and run instructions,
  systemd examples, compose services, download links, badges.
- Protocol and interface text keeps MinIO: MINIO_* variables, minio_* metrics,
  x-minio-* headers, /minio/* routes, .minio.sys, arn:minio, and API field and
  error names.
- Attribution keeps MinIO and gains the fork's own: the AGPL obligations,
  original copyright, CREDITS and NOTICE stay, with the modification notice
  added alongside rather than replacing them.
- Historical and third-party references are left as facts, not rewritten for
  brand tidiness.

README and README_ZH each carry an explicit non-affiliation notice, document
the side-by-side package migration including the
/etc/systemd/system/silo.service.d/10-legacy-user.conf drop-in for keeping a
legacy UID/GID, and state that recursive chown is never performed. The trademark
attribution uses the policy's approved "based on MinIO technology" wording, not
the shortened form the policy rejects.

github.com/pgsty/minio links are left in place and labelled transitional. The
repository has not been renamed, and rewriting them now would produce documented
URLs that 404 until the cutover; they change in the cutover commit together with
the goreleaser release target, the OCI source label and the raw-content branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-06 08:49:30 +08:00

5.8 KiB

Raw Blame History

Silo Server Limits Per Tenant

For optimal production setup Silo recommends Linux kernel version 4.x and later.

Erasure Code (Multiple Drives / Servers)

Item	Specification
Maximum number of servers per cluster	no-limit
Minimum number of servers	02
Minimum number of drives per server when server count is 1	02
Minimum number of drives per server when server count is 2 or 3	01
Minimum number of drives per server when server count is 4	01
Maximum number of drives per server	no-limit
Read quorum	N/2
Write quorum	N/2+1

Limits of S3 API

Item	Specification
Maximum number of buckets	unlimited (we recommend not beyond 500000 buckets) - see NOTE:
Maximum number of objects per bucket	no-limit
Maximum object size	50 TiB
Minimum object size	0 B
Maximum object size per PUT operation	5 TiB
Maximum number of parts per upload	10,000
Part size range	5 MiB to 5 TiB. Last part can be 0 B to 5 TiB
Maximum number of parts returned per list parts request	10000
Maximum number of objects returned per list objects request	1000
Maximum number of multipart uploads returned per list multipart uploads request	1000
Maximum length for bucket names	63
Maximum length for object names	1024
Maximum length for '/' separated object name segment	255
Maximum number of versions per object	10000 (can be configured to higher values but we do not recommend beyond 10000)

NOTE: While Silo does not implement an upper boundary on buckets, cluster hardware has natural limits that depend on workload and scaling patterns. Benchmark the intended workload and size production deployments with operational headroom.

List of Amazon S3 APIs not supported on Silo

We found the following APIs to be redundant or less useful outside of AWS S3. If you have a different view on any of the APIs we missed, please consider opening a GitHub issue with relevant details on why Silo must implement them.

List of Amazon S3 Bucket APIs not supported on Silo

BucketACL (Use bucket policies instead)
BucketCORS (CORS enabled by default on all buckets for all HTTP verbs, you can optionally restrict the CORS domains)
BucketWebsite (Use caddy or nginx)
BucketAnalytics, BucketMetrics, BucketLogging (Use bucket notification APIs)

List of Amazon S3 Object APIs not supported on Silo

ObjectACL (Use bucket policies instead)

Object name restrictions on Silo

Object name restrictions on Silo are governed by OS and filesystem limitations. For example object names that contain characters ^*|\/&"; are unsupported on Windows platform or any other file systems that do not support filenames with special characters.

This list is non exhaustive, it depends on the operating system and filesystem under use - please consult your operating system vendor for a more comprehensive list of special characters.

Silo recommends using Linux operating system for production workloads.

Objects must not have conflicting objects as parent objects, applications using this behavior should change their behavior and use non-conflicting unique keys, for example situations such as following conflicting key patterns are not supported.

PUT <bucketname>/a/b/1.txt
PUT <bucketname>/a/b

PUT <bucketname>/a/b
PUT <bucketname>/a/b/1.txt

5.8 KiB Raw Blame History