What the data for this category looks like
Data for this category comes from the unified budget management system, project declaration materials, fund payment data, business system ledgers, and satisfaction surveys. The update frequency is annual. Daily produced documents include performance target forms, self-assessment forms, performance evaluation reports, supporting material lists, and rectification reports. Document fields include project number, fund amount, performance indicator completion status, supporting material association items, and more. Some fields use preset quantitative units such as item, person-time, etc. Most data is a mix of structured and unstructured formats. Some documents need to be associated with supporting materials from multiple sources, requiring unified parsing and storage adapted to multi-source data.
What constraints these characteristics impose on the deployment and upgrade phase
The annual update feature requires configuring scheduled tasks that support batch import during deployment, to adapt to centralized upload and processing of annual performance data. Mixed processing of multiple types of documents requires configuring file storage and parsing rules compatible with different formats, to avoid field mapping conflicts across different document types. Performance evaluation-related data involves fiscal management processes. The deployment phase must ensure compliance configuration for data storage. At the same time, upgrades must retain version compatibility for historical evaluation data. In addition, scenarios with multiple collaborative subjects require configuring cross-role permission controls, to adapt to access permissions for different users such as finance bureaus and budget units, and avoid sensitive data leaks.
Reference only; verify against the target FastGPT release and deployment documentation.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://localhost:27017/fastgpt | The volume of fiscal expenditure performance evaluation data grows with annual project scale, requiring a stable document database to store unstructured data such as performance reports and self-assessment forms |
REDIS_URL | redis://localhost:6379/0 | Used to cache frequently accessed performance indicator data and user sessions, requiring low-latency memory storage |
STORAGE_S3_ENDPOINT | http://192.168.1.100:9000 | Used to store large-volume files such as supporting materials and rectification reports, adapting to locally privately deployed storage nodes |
DB_MAX_LINK | 20–30 | Stable database connection count must be maintained during fiscal data batch import, to avoid import failures caused by exhausted connections |
FE_DOMAIN | http://localhost:3000 | Used to generate callback addresses for file access tokens, matching the deployment domain name of the frontend service |
FILE_TOKEN_KEY | Custom random string | Used to sign file access tokens, ensuring access security for performance-related documents |
Three Common Mistakes
- Issue: An
internal server errorprompt appears when importing performance evaluation-related plugins. Cause: TheMONGODB_URIorREDIS_URLparameters are not correctly configured, resulting in failed database connections. - Issue: Model vendor icons fail to load after upgrading the version. Cause: Static resource mapping configuration is not updated, or the storage service pointed to by the
STORAGE_S3_ENDPOINTparameter is not running normally. - Issue: Local deployed knowledge base disk usage cannot be viewed. Cause: The system's disk monitoring plugin is not enabled, or the
FILE_TOKEN_KEYparameter is not configured, causing the file storage path to fail to be read correctly.
How to Confirm the Configuration is Complete
- Run the database connection test script to verify that the services pointed to by the
MONGODB_URIandREDIS_URLparameters can connect normally. - Upload a compressed package sample of a performance self-assessment form and supporting materials, confirming that the storage service configured via
STORAGE_S3_ENDPOINTcan receive and store files normally. - Access the frontend address specified by
FE_DOMAIN, confirming that the page loads normally with no configuration error prompts. - Run a batch data import test, importing 10 performance project data entries, confirming that the connection count configuration for the
DB_MAX_LINKparameter can support the import process.
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.