What the Data for This Category Looks Like
Core data for coal transportation and sales originates from internal transportation and sales management systems, vehicle/train weigh tickets, scheduling shift logs, and purchase and sales contract ledgers. Waybill data is generated in real time and updated each time a shipment is completed. Contract ledgers and scheduling logs are updated per daily shift. A single waybill document includes fields such as coal type, rail car/vehicle license plate number, departure location, arrival location, gross/net weight (unit: tons), and shipment timestamp. A single contract document includes fields such as contract number, total contracted volume, settlement unit price (unit: yuan per ton), and information of both contracting parties. Some data includes scanned attachment files, and a single attachment can reach tens of MB in size.
Constraints on Deployment and Upgrade
Real-time waybills have high concurrent write requirements, which require database connection pool configurations to adapt to peak traffic. Mixed storage of multi-field structured data and attachments requires object storage and database configurations to be separated and compatible with large file storage. Differences in update rhythms across different data types require incremental synchronization tasks to use different trigger periods per data type. Deployments for internal office scenarios must adapt to intranet environments, and public exposure of core data interfaces is prohibited. During upgrades, retain the mapping relationship of original business data such as contracts and work orders to avoid business interruptions caused by data structure changes.
How to Configure
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 connections | Adapt to concurrent write and query peaks for real-time waybills, avoid database connection exhaustion |
STORAGE_S3_ENDPOINT | Intranet access endpoint of internal object storage | Store large files such as weigh ticket scans and contract attachments, ensure data transfers within the intranet |
REDIS_URL | redis://intranet Redis address:6379/1 | Cache frequently queried waybill status and employee service work order data, reduce database load |
PG_URL | Intranet connection string of internal PostgreSQL database | Store structured business data such as employee service work orders and contract ledgers |
FE_DOMAIN | https://internal office system domain | Configure front-end access address, adapt to domain name rules for intranet office scenarios |
FILE_TOKEN_KEY | 32-bit randomly generated string | Generate file access tokens, restrict internal documents to access only via authorized links |
Three Common Configuration Mistakes
- After an upgrade, the FastGPT version displayed on the front-end page does not match the actual deployed version. When accessing
FE_DOMAIN, the version identifier at the bottom of the page still shows the old version number. For example, after deploying FastGPT v4.17.0, the page still displays v4.13.1. This occurs because front-end static resources were not rebuilt, and the browser cached the old version file. - A large number of timeout errors appear during real-time waybill data synchronization. Database logs return connection timeout errors, and waybill data cannot be written to the system in a timely manner. This occurs because the
DB_MAX_LINKconfiguration value is too low to support concurrent waybill write requests. - Attachments for employee service work orders cannot be uploaded normally. An upload failure prompt appears when uploading weigh ticket scans, and background logs return a storage endpoint error. This occurs because
STORAGE_S3_ENDPOINTis configured incorrectly and does not point to the correct address of the internal object storage.
How to Verify Configuration Success
- Access the configured
FE_DOMAINaddress, check the version identifier at the bottom of the page, and confirm alignment with the deployed FastGPT version. - Submit simulated waybill data, log in to the corresponding database instance, check whether the data is successfully written to the corresponding data table, and verify that the
PG_URLandDB_MAX_LINKconfigurations take effect. - Upload a test weigh ticket scan, confirm that it can be stored normally and accessed via an authorized link, and verify that the
STORAGE_S3_ENDPOINTconfiguration is correct. - Check the Redis monitoring panel, confirm that the connection count is within a reasonable range, and verify that the
REDIS_URLconfiguration takes effect.
The values provided are common starting points and should be evaluated against local test 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.