RustFS Console
https://github.com/rustfs/console- Category
- Developer Tools
- Rank
- No. 832Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- rustfs
- GitHub
- 177 stars
- Latest release
- v0.1.25
- Date
About
Modern web management console for the RustFS distributed file system — Next.js 16, React 19, Tailwind v4, shadcn/ui.
What it does
RustFS Console gives operators a browser-based control room for files, identities, permissions, storage policies, encryption, events, licensing, and system health. It talks to RustFS administration endpoints and S3 services, turning configuration and object operations into visual workflows.
Why it's ranked here
The appeal is breadth with operational focus. One console covers routine object work, access administration, configuration transfer, monitoring, and less common storage controls. Internationalization across 13 languages and explicit support for signed S3 requests make it useful beyond a narrow demonstration interface.
What's good
The client deduplicates matching in-flight reads, handles streamed newline-delimited JSON, and distinguishes authentication failures from permission failures. Locale resources load on demand, with query, storage, cookie, browser, and document-language detection. Bucket CORS input receives strict field, type, method, and length validation before use.
Tradeoffs
RustFS must run separately, so this is not a standalone storage system. Local development requires Node.js 22 or newer, pnpm 11, and Docker for the documented service setup. The testing guidance is conditional, while the configured test command targets only library tests, leaving broader coverage unclear.
How to use it well
Use it for teams that operate RustFS and prefer visual administration over assembling separate object, identity, policy, monitoring, and storage configuration tools. Run RustFS first, configure its endpoints, then deploy the console on a Next.js-capable platform. It does not replace the RustFS service itself.
Technical notes+
The private ESM package in package.json uses Next.js 16.3.0, React 19, TypeScript 6, pnpm, and Node.js 22 or newer. lib/api-client.ts provides transport injection, GET deduplication, status-aware error handling, JSON parsing, and NDJSON streaming. lib/config.ts resolves runtime, stored-browser, current-browser, or server-default configuration and caches it for 60 seconds. lib/i18n.ts initially loads the default and detected locales, then dynamically imports additional locale JSON and optional theme overrides. lib/aws4fetch.ts implements browser-side AWS Signature Version 4 using node-forge because SubtleCrypto may be unavailable in non-secure contexts. lib/bucket-cors.ts validates and normalizes CORS JSON, while lib/bucket-name.ts applies basic bucket length and uppercase checks.
Observed
- License
- Apache License 2.0
- Primary language
- TypeScript
- Package surface
- Private ESM package managed with pnpm
- Interface
- Browser-based web console using RustFS administration and S3 endpoints
- Runtime requirements
- Node.js 22 or newer and pnpm 11
- Deployment support
- Next.js-capable platforms, including Vercel, Docker, and self-hosting
- Internationalization
- 13 documented languages
Read from README.md, package.json, lib/i18n.ts, lib/config.ts, lib/events.ts, lib/logger.ts, lib/aws4fetch.ts, lib/clipboard.ts, lib/functions.ts, lib/icon-map.tsx, lib/api-client.ts, lib/mime-types.ts, lib/bucket-cors.ts, lib/bucket-name.ts, lib/bucket-path.ts.
What it can do
View distributed file system status
RustFS cluster connection → Real-time system health and performance metrics
Browse distributed file directories
File path navigation requests → Directory listings and file metadata
Upload files to distributed storage
Local files and target directory path → Distributed file storage confirmation and metadata
Download files from distributed storage
File selection from RustFS cluster → Local file download
Manage file permissions and access controls
File paths and permission settings → Updated access control configurations
Monitor cluster node performance
RustFS cluster node identifiers → Node-specific performance analytics and status
Configure distributed file system settings
System configuration parameters → Applied configuration changes across cluster
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.