What the data for this use case looks like
The data for integrated coal and power scenarios comes primarily from real-time monitoring systems for coal mining and power plant production, internal enterprise OA, attendance management, salary calculation platforms, and employee training records. Production-related data updates at a second-to-minute interval. Office-related data updates daily or on demand. Employee record data updates monthly. Data documents include equipment operating parameters, office workflow nodes, employee identity and performance fields. Units include tons, kilowatt-hours, person-times, yuan, and others.
What constraints these characteristics impose on deployment and upgrades
Reference only; verify against the target FastGPT release and deployment documentation. Real-time production data for integrated coal and power scenarios has high update frequency and large data volume. This requires database connections during deployment to support high concurrency and long connections, to avoid timeout interruptions. Multi-source data access must support compatible parameter fields across different formats. During upgrades, ensure data parsing logic between old and new versions is compatible to prevent production data loss. Storage and transmission of employee privacy data must meet compliance requirements. Configure encryption parameters during deployment. Reserve sufficient memory and storage resources for processing batch office workflow data, to avoid service lag.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
MONGODB_URI | mongodb://[username]:[password]@[intranet IP]:27017/fastgpt?authSource=admin | Adapts to multi-source data storage for integrated coal and power scenarios; intranet deployment ensures secure transmission of production data |
DB_MAX_LINK | 500–800 | Meets high-concurrency connection requirements for real-time production data, avoids service interruption caused by exhausted connections |
STORAGE_S3_ENDPOINT | Intranet object storage service address | Stores large volumes of device monitoring logs and employee archive files; intranet access reduces latency and ensures data security |
FE_DOMAIN | https://internal office domain | Adapts to enterprise internal HTTPS access requirements, complies with office scenario security specifications |
FILE_TOKEN_KEY | Random string generated according to enterprise internal key management rules | Encrypts employee file download links, prevents unauthorized access to privacy data |
ROOT_KEY | Only configure during initialization; manage via internal permission system afterward | Restricts super administrator permissions, avoids accidental disruption of production and office services |
Three common configuration mistakes
- Symptom: Running
pnpm devin a local development environment shows a database connection timeout and fails to start the service. Cause: The correct intranetMONGODB_URIis not configured, or the database port is not open in firewall rules, preventing the service from accessing the data source. - Symptom: After Docker deployment, temporary file disk space usage continues to grow, and no safely deletable log files are found. Cause:
STORAGE_S3_ENDPOINTis not configured to use object storage; temporary files are stored locally in the container by default, and no automatic cleanup policy is set. - Symptom: Front-end access to the page fails to load HTTPS resources, and a certificate error appears. Cause:
FE_DOMAINis not correctly configured as an HTTPS address, or the domain SSL certificate is not mounted to the deployment container.
How to confirm the configuration is complete
- Run the database connection test command to verify that the address configured in
MONGODB_URIcan connect normally, with no timeout errors. - Access the configured
FE_DOMAINaddress, confirm that the front-end page loads normally, and internal office functions can be called normally. - Upload a test file to the system, confirm that the file storage path matches the object storage service configured in
STORAGE_S3_ENDPOINT, with no storage errors. - Check the service logs, confirm that the connection number configured in
DB_MAX_LINKdoes not trigger exhaustion alerts, and the service runs stably.
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.