What this category of data looks like
New energy development ledger data comes from SCADA real-time operation systems for wind turbines and photovoltaic power stations, monthly operation and maintenance inspection logs, paper grid connection acceptance documents, and electronic archives. Data update frequencies fall into three groups:
- Real-time: Single device operating power, power generation
- Daily: Operation and maintenance duration, fault count
- Project cycle: Investment details, grid connection date
Each ledger document includes structured fields such as device ID, power generation power (unit: kW), operation and maintenance duration (unit: hours), project name, and investment amount (unit: ten thousand yuan). It also includes unstructured attachments like device operation curves and acceptance reports.
Deployment and upgrade constraints
Multi-source heterogeneous data sources require adaptation to different data source access formats during deployment. Plan storage and indexing strategies ahead of time. High-frequency real-time data updates require high-concurrency cache and database connection pool configurations during deployment. This prevents service freezes caused by insufficient connections. Unit verification requirements for structured fields require field format validation rules during upgrades. This stops erroneous data from being written to the ledger database. Compliant storage of scanned paper documents requires access configuration for approved storage services. This ensures data retention meets regulatory standards. Reference only; verify against the target FastGPT release and deployment documentation.
How to set configuration values
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 | Large volume of new energy development ledger data requires support for concurrent database read and write requests |
MONGODB_URI | mongodb://neuser:nepass@db-host:27017/ne_operation?authSource=admin | Stores real-time operation data and unstructured operation and maintenance ledger attachments |
PG_URL | postgresql://neproject:pgpass@db-host:5432/ne_project | Stores structured project ledger, grid connection acceptance, and investment detail data |
REDIS_URL | redis://:redis_pass@cache-host:6379/0 | Caches high-frequency query daily power generation data to reduce access pressure on the primary database |
STORAGE_S3_ENDPOINT | https://s3-cn-north-1.example.com | Stores compliant paper ledger scan copies and report templates |
FE_DOMAIN | https://ne-report.enterprise.com | Configures the frontend access domain name for generating valid report download links |
ROOT_KEY | 32-bit random string generated per internal enterprise security specifications | Configures system administrator initial access permissions and key association rules |
Three common configuration errors
- Symptom: After starting the container, the platform model list is empty, and model calls return 404 errors or invalid key prompts. Cause: Model keys are not correctly associated with the permission configuration corresponding to
ROOT_KEY, or the container is not restarted to apply modified configurations. - Symptom: Container startup fails after running the docker-compose up command, with database connection timeout errors in logs. Cause: The
DB_MAX_LINKconfiguration value is too low to meet concurrent read and write requirements for multi-device ledger data, or the account password in the database connection string is incorrect. - Symptom: Generated report attachments cannot be downloaded normally, with a permission denied prompt when clicked. Cause: The access key corresponding to
STORAGE_S3_ENDPOINTis not correctly configured, orFE_DOMAINis not added to the storage service's cross-origin access whitelist.
How to verify successful configuration
- Run the docker ps command to confirm all deployed containers are running, with no abnormally exited entries.
- Access the frontend address corresponding to the configured
FE_DOMAIN, log in to the system, and check the built-in database connection detection panel to confirm that the connection status ofMONGODB_URI,PG_URL, andREDIS_URLis normal. - Upload a scanned copy of operation and maintenance logs for a small photovoltaic project, and verify whether the attachment access function works normally using the system-generated download link.
- Call the system's built-in model test interface to verify that the configured model key can return normal response content.
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.