What This Category of Data Looks Like
Data for document and material drafting for new energy development is primarily sourced from project approval documents, environmental impact assessment reports, grid connection application materials, land pre-examination files, and similar materials. Update frequency follows project progression, with three key update nodes: initial project approval, construction phase, and pre-grid connection. Each individual document includes fixed fields: project ID, construction location, installed capacity (unit MW), total investment amount, approval document number. It also carries large-volume attachments such as CAD construction drawings and scanned approval documents.
Constraints on Deployment and Upgrade
The phased, multi-node update nature of new energy development documents requires deployment setups to support incremental synchronization, avoiding repeated loading of old data. Single documents include large-volume attachments and multi-field structures, so storage configurations must support high-throughput object storage and structured data storage. Unified metadata mapping rules must also be configured for specific fields, such as the MW unit for installed capacity. Compliance requirements for internal deployments by state-owned enterprises and public sector entities further restrict access domains and permissions. This limits network configuration boundaries between front-end and back-end systems, preventing unauthorized external access to internal project documents.
Configuration Guidance
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 | New energy development projects often proceed in parallel, resulting in high volumes of concurrent retrieval requests. This range prevents database connection pool exhaustion, ensuring stable parallel processing of multiple projects. |
REDIS_URL | Dedicated Redis instance with access password, 16 GB or more memory | Used to cache document metadata and retrieval results, reducing query pressure on structured databases and supporting caching needs for multi-node deployments. |
STORAGE_S3_ENDPOINT | S3-compatible enterprise-grade object storage endpoint | Adapts to large-volume attachments such as CAD drawings and scanned documents included in new energy development documents, providing high-throughput storage and reading capabilities. |
FILE_TOKEN_KEY | Random encrypted string of 32 characters or more | Generates secure download credentials for document attachments, preventing unauthorized access to internal project documents and meeting data security requirements for state-owned enterprises and public sector entities. |
PG_URL | Dedicated PostgreSQL instance, 1000 GB or more storage capacity | Used to store multi-version project documents and approval records, supporting fast retrieval by project ID and meeting long-term archiving needs. |
FE_DOMAIN | Enterprise internal office domain | Limits front-end access scope to only internal office networks, complying with security specifications for internal deployments by state-owned enterprises and public sector entities. |
Three Common Misconfigurations
- Symptom: Large model responses and knowledge base retrieval results are displayed twice, with duplicate output. Cause: The link between knowledge base retrieval and large model invocation is not properly associated, causing retrieval results to be directly passed to the output stage and resulting in duplicate display.
- Symptom: Storage errors occur when importing large CAD attachments. Cause: The read/write permissions for the storage bucket corresponding to
STORAGE_S3_ENDPOINTare not configured, or the single-file upload size limit is not adjusted, failing to meet the large attachment requirements of new energy development documents. - Symptom: Database timeouts occur during parallel retrieval of multiple projects. Cause: The value of
DB_MAX_LINKis set too low, preventing the database connection pool from supporting concurrent requests and leading to service interruptions.
How to Verify Configurations Are Valid
- Upload an environmental impact assessment report attachment for a new energy development project, verify that storage and preview work properly, and check if the
STORAGE_S3_ENDPOINTconfiguration takes effect. - Initiate three or more parallel project document retrieval requests, confirm that the database connection count stays within the limit set by
DB_MAX_LINK, and verify that the connection pool configuration is working correctly. - Access the enterprise internal domain, verify that the front-end page loads normally, and confirm that the
FE_DOMAINconfiguration complies with internal access rules. - Attempt to download an uploaded document attachment, verify that download links generated using
FILE_TOKEN_KEYare valid and carry no unauthorized access risks.
The values listed here are common starting points, and should be evaluated against the deploying party’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.