What the Data for This Category Looks Like
Reference only; verify against the target FastGPT release and deployment documentation.
What Constraints These Characteristics Impose on the Deployment and Upgrade Phase
The real-time and high-concurrency nature of device operation logs requires reserving sufficient database connection and storage resources during deployment. Maintenance work orders and employee documents include structured and unstructured content, so they need to adapt to the configuration requirements of hybrid storage. Internal office services for rail transit equipment cannot be interrupted, so a rolling update strategy must be used during the upgrade phase to avoid affecting front-line operations and daily employee use. Synchronization of real-time data must be verified before and after the upgrade to prevent data loss or misalignment.
How to Set the Configuration
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 150–200 connections | High concurrent access volume of rail transit equipment logs, prevents database connection pool exhaustion |
STORAGE_S3_ENDPOINT | http://minio:9000 | Adapts to local MinIO storage, used for storing large files such as maintenance photos and device log attachments |
REDIS_URL | redis://:your_password@redis_host:6379/0 | Caches real-time device alarm data to ensure fast response of internal office pages |
MONGODB_URI | mongodb://mongodb_host:27017/fastgpt | Stores structured maintenance work orders and employee training records, adapts to unstructured document storage requirements |
FILE_TOKEN_KEY | Random 32-character string | Ensures access security for maintenance files uploaded by devices, prevents unauthorized access |
Three Common Mistakes
- Symptom: The download speed is lower than 100 KB/s when executing
docker pull fastgpt-minio, with no response for a long time. Cause: No domestic mirror acceleration source is configured, and the default official image repository has high network latency. - Symptom: After upgrading from v4.9.11 to v4.10, historical device logs cannot be loaded normally. Cause: The database corresponding to
MONGODB_URIwas not backed up in advance, and the upgrade script is not compatible with the old data structure. - Symptom: A 504 timeout error occurs when accessing the internal office page. Cause: The
DB_MAX_LINKconfiguration is too low, causing the database connection pool to be exhausted and unable to handle concurrent device data query requests.
How to Confirm the Configuration Is Correct
- Execute the
docker pscommand, confirm that all FastGPT-related containers, MinIO containers, and Redis containers are running, and there are no abnormal exit logs. - Access the domain configured in
FE_DOMAIN, upload a maintenance work order attachment after logging into the system, and verify that the file is uploaded successfully and can be downloaded normally. - Initiate a batch device log query request, check that the number of returned results matches the preset query range, and there are no connection timeouts or error messages.
- On the system knowledge base management page, create a device maintenance document collection, and verify that the collection tag function can be created and associated normally.
- View the storage connection status panel in the system backend, confirm that the connection status of
STORAGE_S3_ENDPOINTandREDIS_URLis normal.
The values given are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.