[majinghe]

Summary

Six new verified integration guides, each in all five locales (en/zh/de/fr/ja) with screenshots (Chinese UI screenshots for zh, English for the other locales):

• ai/sglang — serve LLM inference with model weights streamed directly from a RustFS bucket via the native s3:// model path and the runai streamer (CPU xeon image; verified with Qwen2.5-0.5B-Instruct)
• observability/fluent-bit — CNCF Fluent Bit S3 output with buffered uploads, upload_timeout, and path-style custom endpoints
• devops/helm — private Helm chart repository in a RustFS bucket via the helm-s3 plugin (init → push → search → pull round-trip)
• cloud-native/dapr — Dapr bindings.aws.s3 component with forcePathStyle and create/get round-trip through the sidecar HTTP API
• cloud-native/camel — Apache Camel aws2-s3 producer/consumer YAML routes run with Camel JBang
• big-data/pulsar — Apache Pulsar tiered-storage S3 offload on pulsar-all, with ledger rollover, offload trigger, and cold reads back from the bucket

Every guide documents the exact pitfalls hit during verification (SGLang CPU image missing runai-model-streamer-s3 + uv-only venv; Fluent Bit's absent s3_force_path_style option and NoSuchBucket; helm-s3's AWS_ENDPOINT/AWS_DISABLE_SSL variables and push-by-repo-name semantics; Pulsar's managedLedgerOffload* vs s3ManagedLedgerOffload* key split between the S3 and aws-s3 drivers and its ACCESS_KEY_ID/ACCESS_KEY_SECRET credential envs).

Category meta.json files updated in all five locales to register the new pages.

Notes

• SGLang's native object-storage loading worked against RustFS directly (unlike vLLM 0.30, which needs an rclone mount); the SGLang guide documents the direct path and cross-links the vLLM approach.
• Apache NiFi and Apache Solr were evaluated and skipped: NiFi 2.4's AWS SDK v1 S3 stack fails against RustFS with SignatureDoesNotMatch even in a minimal reproduction, and Solr's S3BackupRepository documents MinIO-class endpoints as unsupported.

Validation

• npm run docs:check: PASS (970 pages, locale tree parity, code-block parity, banned strings, image sizes)
• npm run build: succeeds (3905 static files generated)
• All integrations verified end-to-end on a live RustFS instance: write → confirm object in RustFS → read back

[vercel]

@majinghe is attempting to deploy a commit to the overtrue's projects Team on Vercel.

A member of the Team first needs to authorize it.