Ecosyste.ms: Awesome

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

Awesome Lists | Featured Topics | Projects

https://github.com/karl-sjogren/zebra-deploy

Provides a simple way to deploy websites or services on Windows.
https://github.com/karl-sjogren/zebra-deploy

Last synced: 5 days ago
JSON representation

Provides a simple way to deploy websites or services on Windows.

Awesome Lists containing this project

README

        

# zebra-deploy [![Build status](https://ci.appveyor.com/api/projects/status/b7m20i36frv9u1fo?svg=true)](https://ci.appveyor.com/project/karl-sjogren/zebra-deploy)

Provides a simple way to deploy websites from zip files on IIS.

## Installation

Build the service project and copy the output to your selected location. Execute `ZebraDeploy.Service.exe --install` to install it as a service (has to be run with administrative permissions).

## Configuration

Create a file named config.xml (yes xml, live with it) in your install location. Copy the sample configuration below to start with.

```xml

X:\zebra-deploy\dropzone





















```

**BasePath**
The path which will be watched for new files.

**Stripes**
All zebras have some stripes which in this case would be each website you want to deploy.

**Reporters**
Global reporters that will report on all stripes.

### Stripe configuration

**File**
The name of the file to watch for in the base-path.

**StartAppPool/StopAppPool**
Starts or stops the IIS application pool specified by **name**. Great for applications that keep locking files.

**StartWebsite/StopWebsite**
Starts or stops the IIS website specified by **name**. Great if you want a site to fall through to a "Deploying new stuff"-page.

**Clean**
Removes all files from the specified **path**, can exclude files/folders with the **exclude** element.

**Output**
Extracts the contents for the website into the specified **path** overwriting any existing files.

**Reporters**
Stripe specific reporters that will report on all stripes.

### Reporters

Reporters are invoked when a deployment finishes and can be configured to only notify when succeeding or failing.

#### HipChat reporter

Send information to a hipchat room specified by **room**.

#### Pushover reporter

Send information to Pushover. You need to register an app on pushover.net and enter both the application and user keys in the configuration.

**Priority**

The fields **success-priority** and **failure-priority** can be used to set custom priority levels according to https://pushover.net/api#priority.
The default is -1 for successful deploys and 0 for failures.

#### Slack reporter

Send information to a Slack channel. You need to register an app for Slack and enable incoming webhooks, then put the webhook for the right channel in the configuration.