Home

DropkicK

Welcome to the dropkick wiki! This documentation is a work in progress, to find out more about supported deployments have a look at deployments in the test project. Also have a look at the tests driving the command line.

Features/Requirements

What sets DropkicK apart from other frameworks? See Features.
Will DropkicK even work for you? See Requirements.

Concepts

DropkicK has some core concepts that you should understand prior to using DK. It will help later when you are trying to understand what is going on. Concepts

What is needed for a deployment?

For dropkick to perform a deployment, it needs the following:

• Deployment DLL - A deployment assembly that contains:
  • Deployment Plan - A class that implements dropkick.Configuration.Dsl.Deployment. This defines the roles for your deployment and the deployment steps for each role. See DeploymentPlan.
  • Deployment Settings - A class that inherits from dropkick.Configuration.DropkickConfiguration. This contains configuration properties for your deployment, you can add any properties you like here, these properties will be populated from environment settings file and passed into your deployment class. See DeploymentSettings.
• A settings folder that contains (each of the following per environment):
• Environment Settings File (ENVIRONMENT_NAME.js) - A jsonp format file that gets deserialised into the configuration class. The key should match the name of the property in your configuration (settings) class. See DeploymentSettings.
• ServerMaps File (ENVIRONMENT_NAME.servermaps) - A jsonp format file that specifies the server unto which each role will be installed. The key should match the name of a Role in your deployment class. See ServerMaps.

Running DK

See Execution

Advanced Usage Scenarios

• Setting Name Token Replacement
• Using Tildes In Paths PathTilde
• Auto deploys from TeamCity
• Run Remote Processes