What the data for this category looks like
Survey and design business process data mainly comes from full-cycle project survey reports, design drawing metadata, process approval forms, and on-site inspection records. Project progress triggers data updates. Upload initial materials when a project starts. Modify verification content during approval stages. Freeze data after project archiving. A single document includes fields such as project number, survey point coordinates, design parameters, approval nodes, and handler information. Point coordinates use decimal longitude and latitude units. Design parameters use square meters and cubic meters as units. Approval nodes mark working day durations.
What constraints these characteristics impose during deployment and upgrades
Survey and design data includes multi-format documents and structured forms. The data volume of a single project is large, and update frequency fluctuates with approval stages. During deployment, adapt to mixed scenarios of large-file storage and high-frequency small-data read/write operations. During upgrades, ensure data read/write is not interrupted to avoid project process freezes. Since the data includes professional fields such as longitude and latitude and engineering parameters, database migration must strictly retain field formats and unit consistency. Also, ensure compatibility with arm architecture operating environments to avoid compatibility errors after deployment.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 connections | Survey and design project data has high read/write frequency, requiring sufficient connection pools to handle concurrent requests and avoid database connection exhaustion |
MONGODB_URI | mongodb://[username]:[password]@[host]:[port]/fastgpt?authSource=admin | Store unstructured drawings, reports, and structured metadata for survey and design projects, requiring an independent database instance to ensure data isolation |
REDIS_URL | redis://:[password]@[host]:[port]/0 | Cache approval node and point coordinate data to reduce pressure from high-frequency database read/write operations |
STORAGE_S3_ENDPOINT | Fill in the access address provided by the enterprise object storage service provider | Adapt to the storage needs of large-volume drawings and reports for survey and design projects, support resumable uploads |
ROOT_KEY | Randomly generated 32-character string | Ensure system background access permission security, prevent unauthorized operations from modifying business process configurations |
FE_DOMAIN | https://[enterprise intranet domain]:8080 | Restrict front-end access domain names, adapting to the security requirements of state-owned enterprise intranet deployments |
Three Common Misconfigurations
- Symptom: After performing a version upgrade, the system prompts a database connection timeout, and business process triggering fails. Cause: The
DB_MAX_LINKconfiguration was not adjusted. After the upgrade, the concurrent connection count exceeds the original setting, causing database requests to be rejected. - Symptom: When deployed on an arm architecture Galaxy Kylin Linux system, the Docker container fails to start, and logs prompt that the image architecture is incompatible. Cause: An arm-compatible FastGPT image was not used. The default amd64 image cannot run in an arm environment.
- Symptom: After migrating MongoDB data, survey point coordinate fields display as empty or have abnormal formats. Cause: The decimal longitude and latitude format of the fields was not retained during migration, leading to data parsing errors and inability to properly display professional parameters.
How to Confirm Proper Configuration
- Log in to the system background management page, check the version information module, and confirm that the FastGPT v4.17.0 version number is displayed.
- Upload a survey and design-related document, wait for the storage task to complete, and verify that the file can be previewed and downloaded normally.
- Initiate a simulated business process submission, check whether the approval node configuration loads normally, and there are no field parsing error prompts.
- Connect to the configured Redis instance, check the cache list, and confirm that temporary approval data for survey and design projects exists.
The values provided here are common starting points, and should be evaluated 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.