Requesting support for configuring API write capabilities via the frontend Weibo UI.

[aispx]

Hey there, I'm back. First of all, thanks for your continued support.

After conducting in-depth testing on Shardline, I’ve found that the current setup—involving numerous features, configuration files, and environment variables—remains somewhat complex for actual deployment and operations. Therefore, I suggest further refining the WebUI and Control Plane:

1. WebUI Initialization Wizard

Feature/Frontend selection
Runtime role and listening address
Data directory and storage policy
Token / API Key / Secret configuration
Backend initialization (S3, MinIO, etc.)
Automatic database configuration generation upon first startup

2. Configuration Center

Consolidate core configurations (currently in env vars and config files) into a database-backed configuration center
Automatic validation and persistence of changes made via WebUI
Prioritize reading valid configurations from the database at startup
Use environment variables primarily for initial setup, overrides, and disaster recovery
Encrypt sensitive configurations to avoid storing secrets in plain text

Suggested priority:

Database Configuration
↓
Environment Override
↓
Config File / Defaults

3. S3 Object Storage Pool

Add comprehensive S3 storage pool management:

Endpoint / Bucket / Region
Access Key / Secret Key
TLS / Path Style
Connection testing and health checks
Monitoring for capacity, object count, and read/write throughput
Storage pool status
Multi-S3 instance/provider management
Repository/Tenant → Storage Pool binding
Default storage pool and failover policies

Example:

Shardline Control Plane
│
┌────────────┴────────────┐
│ │
Configuration Storage Pool
│ │
DB / Env / Secrets ┌───────┼───────┐
│ │ │
MinIO S3 S3-2
│ │ │
┌─────────────────┴───────┴───────┐
│ CAS / Xet Storage │
└─────────────────────────────────┘

4. Instance Binding

Allow administrators to explicitly bind the following via the WebUI:

Repository / Tenant → Storage Pool → Backend Instance

Display actual storage capacity, usage rate, deduplication ratio, IOPS, throughput, and health status. Target Architecture

This enables the following structure:

WebUI = Shardline Control Plane
Database = Runtime Configuration Source of Truth
CAS = Unified Storage Layer
S3 Pool = Pluggable Storage Backend

Ultimately, this allows administrators to handle Shardline initialization, configuration, storage binding, and ongoing maintenance without manually editing TOML or .env files or overriding extensive environment variables.