What the data for this category looks like
Survey and design account data primarily comes from point coordinates and geotechnical parameters collected during on-site surveys, structural verification reports and material selection lists from the design phase, and project change visa records. Data update rhythm adjusts with project progress. The cycle for a single special account update is 3 to 7 days. Each account document includes fields such as project unique identifier, point number, detection value, corresponding specification clause, and acceptance status. Field units include meters, megapascals, kilograms, calendar days, and others. Some cross-disciplinary accounts require integrating data from architecture, structure, and electromechanical disciplines.
What constraints these characteristics impose on deployment and upgrade
Survey and design accounts integrate multi-disciplinary data, and individual document sizes are large. Sufficient database storage space must be reserved during deployment. Data update cycles fluctuate with project milestones. During upgrades, ongoing account synchronization tasks must not be interrupted. Otherwise, some point data may be missing. Format differences across cross-disciplinary fields require configuring unified data validation rules during deployment. This prevents confusion of value units from different sources. For local offline deployment, required basic specification data must be cached in advance. This avoids update failures caused by reliance on internet connectivity.
How to set the configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 | Survey and design account data has large volume and many synchronization tasks. Sufficient database connection pool is required to support concurrent requests |
STORAGE_S3_ENDPOINT | Local storage service endpoint address | Survey and design accounts contain a large number of drawings and report files. Local storage reduces cross-node access latency |
REDIS_URL | redis://localhost:6379/0 | Task status and validation rules for account updates must be cached to avoid repeated calculations |
PG_URL | postgresql://user:pass@localhost:5432/fastgpt | Structured account data requires support for complex queries. PostgreSQL supports multi-field associated retrieval |
FILE_TOKEN_KEY | Randomly generated 32-bit string | Download links for account files must be encrypted and validated to prevent unauthorized access |
Three common mistakes
- Symptom: Version number display errors occur after upgrading to a specified version. For example, pulling the v4.8.10 version displays as 4.1.16. Cause: The correct version tag was not specified when pulling the image. An older version image was pulled by mistake.
- Symptom: When configuring DingTalk access, the open platform prompts "Receiving message address verification failed". Cause: A publicly accessible
FE_DOMAINaddress was not configured, or the corresponding port was not opened. This prevents the DingTalk open platform from completing callback verification. - Symptom: After local offline deployment, specification data required for accounts cannot be loaded. Cause: Basic specification data sets were not cached in advance. Data loss occurs due to reliance on internet retrieval.
How to confirm configurations are correct
- Run a database connection test. Confirm that the configured connection pool upper limit supports the planned number of concurrent synchronization tasks.
- Upload a single survey and design account document. Verify that the unauthorized access interception function works normally using the generated download link.
- Start a temporary account synchronization task. Confirm that task status can be cached and updated normally.
- Access the configured frontend domain name. Confirm that the page loads normally and displays the account field structure.
The values provided here are common starting points. They should be evaluated against the user’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.