What the data for this category looks like
Data for this category mainly comes from business documents including coal purchase and sales contracts, volume settlement vouchers, dispatch order slips, and compliance self-inspection documents. Data updates trigger with transportation and sales business nodes. The length of single documents varies widely, from temporary dispatch notices with tens of characters to annual transportation and sales planning plans with thousands of words. Document fields include coal type labels, calorific value parameters, transportation mileage, settlement unit price, carrier qualification number, and other items, with industry-specific units such as tons, yuan per ton, and kilometers.
What constraints these characteristics impose on the deployment and upgrade link
The wide length span and batch upload characteristics of coal transportation and sales documents impose constraints on resource allocation during deployment and compatibility during upgrades. The variable proportion of long documents requires the storage module to reserve sufficient file storage space, while adapting to parsing processes for documents of different lengths. Concentrated uploads of bulk settlement vouchers and monthly reports increase instantaneous load on databases and caches, requiring advance planning of connection pool parameters. Slight differences in the format of transportation and sales documents generated in different periods require compatibility with old version document metadata reading logic during upgrades, to avoid field parsing failures. The deployment link also needs to plan server resources based on peak business demand to ensure normal execution of concurrent tasks.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 | Adapt to database concurrent connection requirements during bulk coal transportation and sales settlement voucher uploads, avoid task interruptions caused by exhausted connections |
STORAGE_S3_ENDPOINT | Point to the intranet address of a privately deployed MinIO node | Used to store various transportation and sales business documents, adapt to storage requirements for large-volume, multi-type files in coal transportation and sales scenarios |
REDIS_URL | Configure as an independent cache instance with memory specification no less than 2000 MB | Cache frequently called transportation and sales document metadata, reduce instantaneous access pressure on the database |
FILE_TOKEN_KEY | 32-digit random hexadecimal string | Used to generate temporary access tokens for transportation and sales documents, ensure access permission security for internal business files |
ROOT_KEY | High-complexity random key | Used for permission verification in system initialization and upgrade processes, ensure the security of core management operations |
FE_DOMAIN | Configure as the system's external access domain name | Used to generate standardized system access paths, adapt to docking requirements of internal business systems |
Three common misconfigurations
- Slow pull speed when deploying MinIO images, with the terminal displaying connection timeout errors. The cause is failure to configure a domestic mirror source to accelerate pulling, leading to high cross-region network latency when pulling official images directly.
- After upgrading to FastGPT v4.17.0, the settlement unit price field of transportation and sales documents cannot be read normally. The cause is failure to adapt to the field naming rules of old version documents, where the upgraded parsing logic does not match historical data.
- When uploading monthly settlement vouchers in bulk, the system returns a 504 gateway timeout status code. The cause is that the
DB_MAX_LINKconfiguration value is too low, unable to support instantaneous concurrent database connection requests.
How to confirm the configuration is correct
- Access the system address configured via
FE_DOMAIN, log in and try to upload a small coal transportation and sales dispatch notice, confirm that the file can be stored and previewed normally. - View the database connection pool monitoring panel, confirm that the current active connection count does not reach the upper limit set by the
DB_MAX_LINKconfiguration. - Call the MinIO intranet interface, verify that the address configured via
STORAGE_S3_ENDPOINTcan read and write test files normally. - Use the
ROOT_KEYto run the system upgrade verification script, confirm that permission verification passes and no error messages are returned.
The values provided 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.