What the data for this category looks like
Shipbuilding declaration materials and case file review data come mainly from single-vessel project design drawings, construction qualification documents, classification society inspection records, and approval and circulation files. Data is organized by project, with update frequency varying by phase. Update frequency is higher during project initiation and block construction phases. Final case files are consolidated before ship delivery. Each material includes fixed fields: hull number, construction batch, material type, inspection date, approval status, and associated drawing number. Units include millimeters for drawing dimensions, tons for ship tonnage, days for project milestones, and more. Individual case file lengths range from hundreds to tens of thousands of characters.
What constraints these characteristics impose on deployment and upgrades
Shipbuilding declaration materials are isolated by project and vary widely in size. Deployments must use exclusive database and storage resources to prevent data interference between projects. The phased update feature requires retaining existing project metadata associations during upgrades. Forcible reset of project configurations is not allowed. The multi-field association logic of single-vessel projects requires matching database connection pool capacity to concurrent requests during deployment. This avoids timeouts during parsing or queries.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 connections | Adapt to concurrent requirements for parallel processing of multiple vessel projects, avoid exhausting database connection pools |
MONGODB_URI | Configure exclusive connection string per project cluster | Store case file metadata for single-vessel projects, achieve data isolation between projects |
REDIS_URL | 192.168.1.100:6379 (adjust based on actual deployment nodes) | Cache frequently queried ship inspection status data, reduce access pressure on core databases |
STORAGE_S3_ENDPOINT | Exclusive endpoint address of the enterprise’s internal object storage | Store large-volume declaration materials such as ship drawings and high-resolution scans |
FILE_TOKEN_KEY | Random key generated per project | Protect download permissions for declaration materials, prevent unauthorized access |
ROOT_KEY | Generated during initial deployment, retain original value during upgrades | Ensure consistency of system administrator permissions, avoid permission configuration errors after upgrades |
Three Common Mistakes
- Phenomenon: After upgrading to FastGPT v4.17.0, the "Unsaved" prompt continuously displays in the upper right corner of the plug-in configuration page for case file review, even when no content has been edited. The prompt remains after clicking save. Cause: The original
FILE_TOKEN_KEYconfiguration value was not retained during the upgrade, causing a mismatch between front-end and back-end permission verification keys, triggering an abnormal save status prompt. - Phenomenon: After deployment, when attempting to upload ship drawing files, the system returns a 403 status code, and files cannot be stored. Cause: Read/write permissions for the storage bucket corresponding to
STORAGE_S3_ENDPOINTwere not correctly configured, preventing the object storage from receiving large-volume declaration material files. - Phenomenon: When batch importing declaration materials for multiple vessel projects, some document parsing fails, returning a "request timeout" prompt. Cause: The value of
DB_MAX_LINKwas not adjusted, so the database connection pool cannot support parallel parsing requests for multiple materials.
How to Verify Proper Configuration
- Log in to the FastGPT backend, enter the application configuration page for shipbuilding case file review, generate a test declaration material download link, and confirm the link can be accessed normally with no permission errors.
- View the system monitoring panel, confirm the database connection count stays within the configured range of
DB_MAX_LINK, with no connection exhaustion alerts. - Perform a batch import test, import 10 simulated ship drawing files, and confirm all files can be uploaded normally and associated with the corresponding project case files.
- Enter the plug-in editing page, edit any configuration item and save, and confirm the save status prompt in the upper right corner automatically disappears after saving is complete.
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.