fix: mentioning DI in redeployment on sas 9
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 2m43s

This commit is contained in:
allan
2025-07-02 16:22:22 +01:00
parent 92f2f4f6d2
commit 4c45779312

View File

@ -169,12 +169,13 @@ The full redeployment process is as follows:
- To a new metadata folder - To a new metadata folder
- To a new frontend folder (if full deploy) - To a new frontend folder (if full deploy)
* _Delete_ the **new** DC library (metadata + physical tables) * _Delete_ the **new** DC library (metadata + physical tables)
* _Move_ the **old** DC library (metadata only) to the new DC metadata folder * _Move_ the **old** DC library (metadata only) to the new DC metadata folder. You will need to use DI Studio to do this (you can't move folders using SAS Management Console)
* Copy the _content_ of the old `services/public/Data_Controller_Settings` STP to the new one * Copy the _content_ of the old `services/public/Data_Controller_Settings` STP to the new one
- This will link the new DC instance to the old DC library / logs directory - This will link the new DC instance to the old DC library / logs directory
- It will also re-apply any site-specific DC mods - It will also re-apply any site-specific DC mods
* Run any/all DB migrations between the old and new DC version * Run any/all DB migrations between the old and new DC version
- See [migrations](https://git.datacontroller.io/dc/dc/src/branch/main/sas/sasjs/db/migrations) folder - See [migrations](https://git.datacontroller.io/dc/dc/src/branch/main/sas/sasjs/db/migrations) folder
- Update the metadata of the SAS Library, using DI Studio, to capture the model changes
* Test and make sure the new instance works as expected * Test and make sure the new instance works as expected
* Delete (or rename) the **old** instance * Delete (or rename) the **old** instance
- Metadata + frontend, NOT the underlying DC library data - Metadata + frontend, NOT the underlying DC library data