What data for this category looks like
Coal transportation and sales ledger data comes from weighing systems, waybill management systems, and settlement reconciliation systems. A single ledger record includes fields such as waybill number, mining point name, receiving entity, shipment tonnage, settlement unit price, freight amount, completion date, and others. Units include ton, yuan, and trip. Data generates in real time as each individual business completes. A full daily transportation and sales summary document generates at the end of each day. The number of fields in each summary document is fixed, with no dynamically added fields.
What constraints these characteristics impose on deployment and upgrades
The fixed field structure of coal transportation and sales ledgers requires pre-configured structured data mapping rules during deployment. This avoids field parsing errors. Real-time single-record data and end-of-day summary documents use a mixed update rhythm. This creates short-term database read and write peaks. Reserve sufficient connection resources for this load. During upgrades, retain the original ledger's field mapping logic. Failure to do so prevents normal reading of historical data. Also, maintain compatibility with newly added transportation and sales business fields. This prevents failure of the summary logic.
How to configure settings
The following configurations apply to FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 | Handles mixed read/write peaks from real-time single-record data and end-of-day summaries |
REDIS_URL | redis://:{password}@{host}:6379/0 | Caches temporary calculation results of real-time ledgers to reduce database pressure |
PG_URL | postgresql://{user}:{password}@{host}:5432/fastgpt_coal | Stores structured ledger data to support complex summary queries |
STORAGE_S3_ENDPOINT | Fill in according to the local object storage service address | Stores large-volume end-of-day summary documents to avoid occupying database storage space |
ROOT_KEY | Randomly generated 32-bit string | Ensures permission security for system background operations and prevents unauthorized access |
FE_DOMAIN | http://locally deployed domain:port | Configures the system frontend access address for third-party interface permission verification |
Three common misconfigurations
- Phenomenon: After running the local private deployment upgrade script, summary data of historical ledgers fails to load normally. Cause: The original structured ledger field mapping rules were not retained during the upgrade, causing the system to fail to parse the field format of legacy data.
- Phenomenon: After configuring a third-party large model key, a 403 status code is returned during invocation. Cause: The
FE_DOMAINparameter was not configured correctly, and the locally deployed access domain name was not added to the allow list, causing key verification to fail. - Phenomenon: After deploying via docker compose, new system users cannot be created. Cause: User registration function was not enabled in the deployment configuration, or the permission scope of
ROOT_KEYwas not set correctly, preventing administrators from assigning permissions to new users.
How to verify correct configuration
- View the system's built-in database connection monitoring panel to confirm that the current number of connections does not exceed the configured
DB_MAX_LINKvalue. - Import a standard coal transportation and sales ledger sample to check whether the system can fully extract preset fields such as waybill number and shipment tonnage, with no parsing error prompts.
- Trigger an end-of-day summary task to check whether the generated report covers all pending summary business data with no missing items.
- After configuring a third-party large model key, initiate a test conversation to confirm that no permission error is reported for interface calls.
The values provided are common starting points and should be evaluated against sample data specific to the target deployment.
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.