Sitefinity has the following modes for storing configuration files:
Environment configurations can be made read-only on the Live environment.
Limitations: Synchronization of labels and messages between the nodes of a load-balanced environment has to be done manually.
For more information, see NLB: Synchronize labels and messages between the nodes from a load balanced setup.
NOTE: By default, Sitefinity CMS uses Auto-storage mode for its configurations. This is the recommended configuration storage option. FileSystem and Database storage modes are legacy options and are available for backward compatibility.
Configurations are stored on the file system
Advantages: This storage method allows you to apply configuration transformations during delivery easily.
Configurations are stored on the FileSystem, but on shared location.
Configurations are stored in the Database
Advantages: This storage mode allowed for safe runtime modification of application settings when load-balanced.
Limitations: If different environments are required, different configuration values are harder to maintain if needed.
The following table summarizes the applications of the different configuration storage modes:
IMPORTANT: When using database or FileSystem storage, you cannot use Continuous delivery. You can switch from database storage to FileSystem storage mode by migrating the configurations. For more information, see Migrate configurations. To work in Auto-storage mode and use Continuous delivery, you can switch from FileSystem storage mode to Auto-storage mode. For more information, see Turn on Auto-storage mode for configurations.
Once you switch to Auto-storage mode, you cannot get back to the other configuration storage modes.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2019 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.
Powered by Progress Sitefinity