-
Notifications
You must be signed in to change notification settings - Fork 43
Execution
The syntax for running drop kick is:
dk.exe [command] /environment:ENVIRONMENT_NAME [/ARG_NAME:VALUE] [--SWITCH_NAME]
##Commands
[trace|verify|execute]
do a fake run of the deployment without affecting system.
Verifies you settings and deployments is correctly configured.
perform the deployment.
/environment /roles /settings /deployment
DK expects you to pass in the environment you are targeting. This is core to setting up what settings files and servermaps it will be looking for when executing. If you pass in LOCAL, it will start to look for LOCAL.js and LOCAL.servermaps.
/environment:LOCAL
The name of the role you want to deploy. If missing, the default is to deploy all roles.
/roles:Web,Host
Path to the directory containing the settings files. Default is '.\settings' relative to the current working directory.
/settings:..\settings
The assembly or class to use for the deployment. If argument is missing, dropkick will search for a dll ending with 'Deployment' then pass that name in as the deployment assembly. The default is relative to where dk is, not the current working directory. (NOTE: We have talked about changing this behavior to scan the current directory instead of dk.exe directory)
/deployment:..\deploys\somename.deployment.dll
- SomeName.Deployment.dll (path to the assembly containing your deployment class)
- OR SomeName.Deployment.StandardDepoy (a classname, lack of .dll)
--silent
Unattended installation (this is a new feature, so some tasks may not yet adhere to it)
--silent
dk.exe execute
Deploys all roles to 'LOCAL' environment with 'Deployment.dll' (seated next to dk.exe) looking for '.\settings\LOCAL.servermaps' and '.\settings\LOCAL.js'
dk.exe execute /deployment:..\deployments\somename.deployment.dll /environment:LOCAL /settings:..\settings /roles:Web,Host
dk.exe execute /environment:DEV --silent
You can also run dk /? for current help settings.