These screens make database schema modifications, therefore, these changes are done only on the development environment and then promoted via the Export for deployment functionality. When running Export for Deployment, the database schema changes are exported on the file system in the ~/App_Data/Sitefinity/Configuration/Deployment folder. The exported files should then be added to the project and committed to the source code.
Afterwards, the changes can be promoted to Staging and then to Production. Every time Sitefinity starts, it checks the ~/App_Data/Sitefinity/Configuration/Deployment folder and applies any changes detected there. For more information, see https://www.progress.com/documentation/sitefinity-cms/cloud/deploy-database-changes
The workflow looks like this:
Schema changes are made on the Development environment
Use Export for Deployment locally in the Development environment.
Include Deployment folder in the Sitefinity project, if missing, and add new files in the folder.
Commit the changes in the source code .
Deploy to Staging.
Promote to Production, if all changes work as expected on Staging.
For more information, see Export and deploy code changes.
| Sitefinity Cloud
Achieve operational efficiency and drive business growth.
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.