The following XML pseudocode describes the <episerver.packaging> section of the configuration file. The Configuration topic describes the syntax used in the description of the configuration elements.
<episerver.packaging>
<packageRepositories/>
</episerver.packaging>
<episerver.packaging>
XML
<episerver.packaging repositoryPath="string"
publicVirtualPath="string"
publicPath="string"
protectedVirtualPath="string"
protectedPath="string"
packagesTemporaryFolder="string"
packageListCacheTime="TimeSpan"
allowPrereleaseVersions="bool"
allowUnlisted="bool"
installationMode="InstallationMode"
>
<a href="#packageRepositories"><packageRepositories /></a>
</episerver.packaging>
<episerver.packaging> Element Attributes
| Name | Default Value | Description |
|---|
| allowPrereleaseVersions |
false |
Indicates whether pre-release package versions can be installed on site. |
| allowUnlisted |
false |
Indicates whether unlisted packages can be installed on site. |
| installationMode |
UI |
Indicates where add-ons are installed. Set to Code to manage add-ons from Visual Studio, see also Installing add-ons. |
| packageListCacheTime |
0.0:5:0 |
The length of time that package listings from remote repositories are cached. |
| packagesTemporaryFolder |
|
Uploaded and cached packages are temporarily stored in this location. If no value is configured the system designated temporary directory is used. |
| protectedPath |
|
Physical path where protected add-ons should be installed. This value is set to Siteroot\modules\_protected\ during installation. |
| protectedVirtualPath |
|
Virtual path where protected add-ons are installed. During installation this value is set to ~/<EPiServerProtectedPath>/modules where ~/<EPiServerProtectedPath> is equal to protected virtual root path for Episerver dashboard and user interface. |
| publicPath |
|
Physical path where public add-ons should be installed. During installation this value is set to physical path to modules subfolder in the site root directory. |
| publicVirtualPath |
|
Virtual path where public add-ons are installed. During installation this value is set to ~/modules and is equal to virtual root path to public Shell modules. |
| repositoryPath |
|
Installed packages are stored in this location. During installation this value is set to subpath in site VPP directory, for example C:\EPiServer\VPP\<SiteName>\ModulesRepository. |
Note that virtual path providers should be configured to map virtual paths of public and protected add-ons to corresponding physical paths where public and protected add-ons are installed. By default, additional virtual path provider is registered to map virtual and physical paths for protected add-ons.
<packageRepositories>
XML
<packageRepositories>
<add name="string"
url="string"
isEnabled="bool"
apiKey="string"
requestApiKey="bool"
sendLicense="bool"
filterTag="string" />
...
</packageRepositories>
<add> Element Attributes
| Name | Default Value | Description |
|---|
| name |
|
Required. A unique name identifying this package repository. |
| url |
|
Required. The full URL or path to the package repository. |
| isEnabled |
true |
Enables or disables this repository. |
| apiKey |
|
If you have a static API key for accessing this repository, it should be set here. |
| filterTag |
|
If this is set, only packages with this tag set are included in the listing. (This can be used to separate listings based on the same repository url.) |
| requestApiKey |
false |
If you want to request an API key from the repository this option should be enabled. (This is required for the default Episerver repository.) |
| sendLicense |
false |
Whether your Episerver license information should be included with the API key request. (This is required for the default Episerver repository.) |
Default Episerver repository
Episerver central repository feed is added to the packageRepositories collection implicitly by default. You can remove this default repository repository using clear statement.
XML
<packageRepositories>
<clear />
<add name="string" url="string" />
</packageRepositories>
Do you find this information helpful? Please log in to provide feedback.
Area:
Optimizely CMS
