What the data for this category looks like
Internal office data for urban water utilities comes from pipe network pressure and flow monitoring devices, smart water meters, pump station control systems, water quality testing laboratories, internal work order systems, and employee patrol records. Update rhythms fall into three categories: real-time monitoring data is updated every second, meter reading data is updated in daily or weekly batches, and patrol reports and water quality test reports are updated per work cycle. Document structures include structured time-series data (containing node ID, monitoring value, collection time, and unit) and unstructured documents (containing work order number, processing status, responsible person, and attached photos). Fields include exclusive water utility device codes, pipe network topology identifiers, and similar items.
What constraints these characteristics impose on deployment and upgrade
Reference only; verify against the target FastGPT release and deployment documentation.
How to set configurations
| Config Item | Recommended Approach | Rationale |
|---|---|---|
REDIS_URL | redis://:custom_password@internal_redis_service_address:6379/0 | Cache real-time pipe network monitoring data to reduce database query pressure and meet second-level data update requirements |
PG_URL | postgresql://database_username:database_password@internal_pg_address:5432/water_office_db | Store structured meter reading data, work order records, and employee information to support complex business queries |
STORAGE_S3_ENDPOINT | internal_minio_service_address:9000 | Store unstructured files such as patrol photos and water quality test reports, complying with internal network data storage compliance requirements |
DB_MAX_LINK | 200–300 connections | Adapt to the high concurrent real-time data reporting and work order processing requests of water utility systems, avoiding database connection exhaustion |
FILE_TOKEN_KEY | 32-bit random string generated in accordance with internal security specifications | Encrypt file access tokens to prevent unauthorized access to sensitive water utility business files |
FE_DOMAIN | internal_domain:port or local_ip:port | Adapt to internal network deployment scenarios, avoiding public exposure of internal office services |
Three common mistakes
- Symptom: After internal network-only private deployment, the workflow editing interface displays a client exception error. Cause: The internally accessible
FE_DOMAINis not configured, and front-end static resources are not packaged offline in advance, resulting in failure to load necessary front-end dependencies. - Symptom: An error indicating the rehype-raw module cannot be found is prompted when building the Docker image, even after executing the installation command. Cause: The dependency installation did not specify an internal network offline source, or offline dependency packages were not fully imported into the image build directory, resulting in failed dependency pulling.
- Symptom: The Docker container restarts continuously after startup and cannot access the service normally. Cause: The
MONGODB_URIorPG_URLconfiguration is incorrect, database connection verification fails, and the service exits automatically after startup due to inability to connect to dependent services.
How to verify successful configuration
- Access the configured
FE_DOMAINaddress to confirm that the front-end page loads normally with no resource loading failure prompts. - Execute the database connectivity test script to verify that services corresponding to
REDIS_URL,PG_URL, andMONGODB_URIcan all establish normal connections. - Upload a small patrol photo file to confirm that the file can be stored normally and can be previewed normally through the generated access link.
- Submit a test work order to confirm that data can be written to the database normally with no timeout or write failure prompts.
All provided configuration values are common starting points and should be evaluated against the specific samples applicable to the deployment scenario.
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.