What data falls under this category
This category of data includes risk identification lists, hot work/permit-required confined space/hoisting work permits, hazardous waste ledgers, emission monitoring records, accident and hidden danger rectification reports, and similar documents. Data sources include industry regulatory standards, online environmental monitoring equipment, gas detector readings, operator qualification documents, equipment isolation lists, and local supervision platforms. Updates are triggered by work processes: work permits and risk records are updated once a single job is completed. Emission data is synced per monitoring cycle. Qualifications and ledgers are checked monthly or quarterly. Document fields include operation time, gas concentration value, guardian qualification number, isolated equipment number, and similar fields. Some fields use dedicated units such as ppm, cubic meters, and hours.
What constraints these characteristics impose on deployment and upgrade
This category of compliance documents is tightly integrated with real-time monitoring data. It has high update frequency and must meet safety and environmental compliance requirements. Prioritize data storage stability and permission isolation during deployment and upgrade. Multi-source data access requires reserving interface space to adapt to different devices and supervision platforms during deployment. Upgrade processes must avoid interrupting data synchronization, as this causes record loss. Field differences between different document types are significant. Preset the corresponding data models during deployment to avoid field incompatibility issues after upgrade. Access permissions for safety-related documents must be strictly controlled. Configure role permission rules synchronously during deployment to prevent unauthorized access.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | Dedicated connection string pointing to the enterprise compliance document repository | This category requires storing large volumes of structured and unstructured compliance documents. A dedicated database ensures read/write performance and data isolation |
REDIS_URL | Configured as a locally deployed Redis instance, with memory quota set to 1000 MB | High-frequency job data synchronization and permission verification require low-latency cache support. 1000 MB covers daily average job data caching requirements |
DB_MAX_LINK | Set to 80–120 connections | This category has frequent data updates. A reasonable connection limit prevents database connection exhaustion and ensures stability for multi-terminal access |
FE_DOMAIN | Fill in the access domain name of the enterprise internal EHS system | Ensures generated process documents and abnormal reports can be directly synchronized to the internal system, reducing manual import steps |
STORAGE_S3_ENDPOINT | Endpoint address connected to the enterprise’s existing object storage service | Used to store large-volume compliance data such as gas detector original readings and work permit scan copies |
Three common mistakes
- A startup error reports that the
config.jsonfile cannot be located. This happens because the new environment variable configuration logic was not switched to after the upgrade, the old configuration file is still relied on, and the corresponding environment variables were not properly configured. - The system version displayed after deployment is an older version and does not match the target version. This occurs because no explicit version tag was specified when pulling the image, and the default latest old version image from the repository was pulled instead.
- All job records and monitoring data are empty after upgrade. This happens because the original database data volume mount configuration was not retained, and the original database storage content was cleared during container upgrade.
How to confirm configurations are correct
- Access the FastGPT backend, view the system version information, and confirm that FastGPT v4.17.0 is displayed.
- Submit a simulated work permit data record, and verify that storage and synchronization to the specified database instance is completed within
5 seconds. - Access the configured
FE_DOMAINaddress, and confirm that the generated document link can normally redirect to the internal EHS system. - Check the Redis connection status, and confirm that cached job data can be updated normally within
300 seconds.
The values provided are common starting points and should be measured against the reader's own samples.