What data for this category looks like
This category of data typically comes from Figma or Axure prototype files, internal team design systems, user feedback records, and usability test results. Daily deliverables include interactive prototype drafts, page flowcharts, component property descriptions, and design review records. Data update frequency is usually once per week or synchronized with product version iterations. Core fields include page jump paths, interaction trigger logic, component style specifications, and review comments. There are no uniform mandatory units; adjustments are made based on specific design projects.
What constraints these characteristics impose on deployment and upgrades
Data for this category relies on structured files exported from design tools and internal team review records. During deployment and upgrades, configurations must align with the current version’s prototype logic and design system specifications. Since data update frequency follows version iterations, associated configurations of historical prototype versions must be retained during upgrades to avoid a disconnect between development and design documentation after launch. Design-related static resources and interaction logic parameters must also match configuration items stored in the database. If data sources change or formats are adjusted, deployment link reading rules must be updated synchronously to prevent path parsing errors.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@host:27017/fastgpt_design?authSource=admin | Stores prototype file metadata, review records, and design system configurations; must specify the corresponding business database |
PG_URL | postgresql://user:pass@pg-host:5432/design_db?sslmode=require | Stores structured design data such as interaction path configurations and component properties; enable SSL to ensure data transmission security |
DB_MAX_LINK | 20–30 | Adapts to concurrent requirements for batch reading of design documents, and prevents database connection exhaustion |
REDIS_URL | redis://:redis-pass@redis-host:6379/0 | Caches frequently accessed prototype preview links and design review status to reduce database query pressure |
FE_DOMAIN | https://design.your-domain.com | Configures the frontend service access domain name for generating accessible prototype preview links |
FILE_TOKEN_KEY | Random 32-character string | Encrypts prototype file access tokens to prevent unauthorized access to design documents |
Three common errors
- Symptom: After restarting the Docker container, all prototype preview configurations and design system association parameters are lost. Cause: The database was not mounted to local persistent storage. The
PG_URLandMONGODB_URIconfigurations inside the container are only stored in the container’s temporary directory, and data is cleared after restart. - Symptom: After uploading an Axure prototype file, page paths cannot be parsed normally. Cause:
FILE_TOKEN_KEYwas not configured correctly, resulting in failed file access permission verification, and structured data inside the prototype file cannot be read. - Symptom: Design review records cannot be loaded normally after an upgrade. Cause:
DB_MAX_LINKvalues were not updated synchronously, resulting in insufficient database connections, and review record data cannot be pulled in batches.
How to confirm configurations are properly set
- Run a database connection test script to verify connectivity for the
MONGODB_URIandPG_URLconfigurations, and confirm stored design data can be read. - Access the domain configured in
FE_DOMAINto verify that prototype preview links open normally, and confirm the encryption logic of theFILE_TOKEN_KEYconfiguration is effective. - Restart the Docker container and check if design configuration data in the database is retained, to confirm persistent storage configuration is correct.
- For FastGPT v4.17.0, batch upload multiple prototype files to verify the
DB_MAX_LINKconfiguration supports concurrent read requests without connection timeout errors.
The values provided are common starting points and should be measured 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-10-19.