Should the portal attempt to check for the existence of the repository configuration files and default content on startup?
• DefaultContentLocation: Location of the default content used to pre-populate the repository. • DefaultLocale: Two-letter abbreviation of the default locale the portal should use when fetching content for users. A complete ISO-639 list can be found here . • HomeDir: Location of configuration information for the repository when in 100% FileSystem store mode. Otherwise, its in the database.
Related Questions
- When a new version is installed, what does it do to the existing configuration files? Are system default files/entries created, or will existing configuration files be used by the new version?
- Should the portal attempt to check for the existence of the repository configuration files and default content on startup?
- How to reconfigure database console configuration files without loosing configuration information within the repository?