Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/iowacomputergurus/dnn.packagedeployer

A utility application for the deploying of DNN modules, helpful for those with larger DNN solutions and multiple install packages.
https://github.com/iowacomputergurus/dnn.packagedeployer

deployment dnn dotnetnuke

Last synced: 6 days ago
JSON representation

A utility application for the deploying of DNN modules, helpful for those with larger DNN solutions and multiple install packages.

Awesome Lists containing this project

README

        

# dnn.packageDeployer
[![Build status](https://ci.appveyor.com/api/projects/status/c9b5ohc85p6s9ic7?svg=true)](https://ci.appveyor.com/project/IowaComputerGurus/dnn-packagedeployer)

A utility application for the deploying of DNN modules, helpful for those with larger DNN solutions and multiple install packages.

## Configuration
The following information is defined in the local configuration file for the executable





Using this you will wan to configure the utility to run in your environment. The below table details the configuration options.
Setting | Value
--- | ---
RootSearchPath | This is the folder path, absolute or relative, to the source code installation
DeployToPath | This is the folder path to the location that will be used to store all install packages to prepare for installation
PackageDirectoryName | The name of the folder where your actual installation packages are found. Older package format was packages.

## Usage

The current version of this utility is geared towards developer support. Retreiving all of the individual DNN packages from a single directory. Future versions of this utility will add the ability to push to a remote location, and ideally, eventually trigger an upgrade with status reporting.

To use in your environment download the latest release, extract the files to a location as desired, and then run.

## Logging

Each execution of the application will log to both the console and an execution.log file stored in the same folder as the application. This can be helpful for reporting.