What this category of data looks like
Coal transportation and sales declaration materials and file data mainly come from internal transportation and sales management systems, weighing terminals, and ownership qualification databases. Data is generated when each batch of transportation and sales business is triggered, with no fixed batch update cycle. A single file contains fixed fields: mine site name, actual transportation volume (unit: ton), declaration batch number, verification node time. Supporting attachments include weighing slip scans, VAT invoices, and ownership certification documents. Some aggregated file texts can reach thousands of characters.
What constraints do these characteristics impose on deployment and upgrade
The dynamic generation of single-batch data for coal transportation and sales declaration materials and files, multi-type attachments, and structured fields with units imposes multiple constraints on deployment and upgrade. Dynamic single-batch data requires support for dynamic interface access during deployment to adapt to real-time data pushes from business systems. Fields like transportation volume with tons as the unit, and file structures mixing scans and text, require configuration of vector generation logic that supports multi-format file parsing and retention of unit semantics during deployment. The upgrade process must be compatible with newly added transportation and sales qualification fields to avoid failure of knowledge base field mapping, while ensuring the original data parsing link is not damaged. For local deployment scenarios, local file upload configuration must match local network access paths to prevent file upload failures.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
FE_DOMAIN | http://192.168.1.100:3000 (local deployment) or https://yunxiao.your-company.com | Matches local or online access domain names, resolves cross-origin issues for local file uploads in coal transportation and sales business, and ensures attachments can be properly uploaded to the knowledge base |
STORAGE_S3_ENDPOINT | http://127.0.0.1:9000 (local MinIO) or dedicated endpoint from cloud storage service provider | Persistently stores multi-type attachments in coal transportation and sales files, including weighing slip scans and VAT invoices, to meet business file storage requirements |
DB_MAX_LINK | 1500–2500 | Adapts to concurrent scenarios where multiple files from a single batch are accessed simultaneously, prevents database connection exhaustion, and ensures stability of the review process |
REDIS_URL | redis://default:your-redis-password@localhost:6379/0 | Caches intermediate data from file parsing, improves response speed for batch declaration material reviews |
FILE_TOKEN_KEY | Custom 32-character random string | Generates temporary verification tokens for file uploads, ensures security of sensitive business files for coal transportation and sales |
Three common mistakes
- Symptom: Uploading a weighing slip scan fails during local deployment, with the interface showing cross-origin errors or file access failures. Cause: The
FE_DOMAINconfiguration does not match the actual access address of the local server, preventing the frontend from generating correct upload requests. - Symptom: An ERRO-level log appears after executing
docker-compose up -din a Windows environment, and the service fails to start. Cause: Database or storage connection parameters are not configured correctly, preventing FastGPT from initializing the storage and index link for transportation and sales files. - Symptom: FastGPT prompts a mkdir failure when starting in a WSL2 environment, unable to create mount directories. Cause: Improper file system permission configuration for WSL2, or the mount path contains unsupported special characters, preventing the creation of temporary directories for file storage.
How to confirm configurations are correct
- Upload a coal transportation and sales weighing slip scan, check if the file can be stored normally and indexed, confirming that core storage and access configurations are effective.
- Perform a database connection verification operation, confirm that the database connection parameters can establish a normal link.
- Review service running logs, check for errors related to file uploads or database connections, confirming that basic configurations are correct.
- Initiate a simulated declaration material review request, confirm that the service can normally parse structured fields and attachment content in files.
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.