What this category's data looks like
This page addresses the deployment, operations, and application handover stage in academic education management at technical colleges. The source material is the operation records of the deployment environment and the administrator version upgrade page. The update cadence follows version releases and migration task execution batches. Field characteristics center on three categories: image version identifiers, migration task records, and data row index status. When the student registration table, teaching plan, and skills training records enter this function, they respectively take on the role of verifying whether fields and date signatures are consistent before and after deployment: the student registration table is used to confirm that fields are complete after the data row index status migration, the teaching plan is used to compare dates and quantities in task records after version synchronization, and the skills training records are used to verify whether signatures and receipts are complete after migration task execution. During handover, the three materials must correspond item by item with the deployment status, avoiding mismatches in names, quantities, and dates for the same record across two materials.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image version, migration task records, and data row index status. "Handover-ready deployment status and operation records" is then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images are the same target version; check the version identifiers of both images against the version notes | In the deployment environment, check whether the image tags of fastgpt-app and fastgpt-pro are both v4.17.2, and record the image version identifiers |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired; view the execution record of this task on the administrator version upgrade page | Check the dates and signatures in the student registration table, teaching plan, and skills training records, and confirm that the migration task records match the material names and quantities |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete; compare the time and status of the two records | Compare the time and status of the two migration task records, sample one data row to check the index status field, and confirm there are no missing signatures or receipts |
| Data row index status | After migration it is a new index status system; sample one data row to check the status field | Sample one data row to check the status field, and check whether the MONGODB_URI, PG_URL, and REDIS_URL connection records are consistent with the migration task records |
Three common errors
- Symptom: the service can start but the data row status is still the old marker. Cause: the knowledge base rebuild status migration was not executed or not completed, and the data row index status has not entered the new system.
- Symptom: the name, quantity, and date of the same record do not match between the student registration table and the skills training records. Cause: the migration task records and business materials were not checked item by item against the handover sheet, and signatures or receipts are missing.
- Symptom: the two image versions are inconsistent or the script execution reports an error. Cause: the main service and commercial edition images were not updated synchronously, or the migration was triggered before the old instance was fully stopped and the old task lease expired.
How to verify the setup
This function's acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in order, and check the MONGODB_URI, PG_URL, and REDIS_URL connection records and the data row index status field.
Business test: check item by item against the handover sheet once, see which record is missing, and confirm that the version, connections, and task records are consistent.
- On the administrator version upgrade page, view the execution records of the historical chunk training task migration and the knowledge base rebuild status migration, and compare the time and status.
- Sample one data row to check the index status field, and check whether the
DB_MAX_LINKconnection record corresponds to the migration task records.