Powershell deployment scripts for windows services, creating message queues and other common tasks for Octopus deployments.
Powershell scripts:
- Deploying and installing NServiceBus endpoints as windows services
- Deploying and installing TopShelf windows services
- Deploying and installing standard .exe executables as windows services
- Creating Microsoft Message Queues (MSMQ)
- Deploying SQL Databases from Data-tier Application (DAC) files
nservicebus\Deploy.ps1
Installs an NServiceBus endpoint as a windows service. If a service with the same name already exists, it will be stopped and uninstalled fro the system BEFORE deploying the executable from the Octopus nuget package.
This script can also be used to provision a new system by installing the NServiceBus infrastructure, RavenDB, MSMQ, and DTC before installing the service (NServiceBus 3.x only!).
nservicebus\Deploy.ps1
Installs a TopShelf service using the default HostFactory definition (generally in Program.cs). the service with the same name already exists it will be stopped and reconfigured to use the service executable from this deployed octopus package.
msmq\PreDeploy.ps1
Pre deployment script that creates the required message queues (MSMQ). This script accepts either a list of queue names, or the name of a file containing the queues to create.
The preferred mode of use is to define a $MessageQueueNames variable in the Octopus Web Portal. This allows
queues to be created on a per-machine & per-environment basis. Useful for provisioning private queues in test environments
and public TCP queues for production.
mssql dac\Deploy.ps1
Publishes a data-tier application (DAC) from a compiled DAC package to an existing SQL Database, Incrementally updating the database schema to match the source .dacpac file. If the database does not exist on the server, the publish operation will deploy, otherwise an existing database will be updated.
This script is compatibile with Visual Studio 2012 SQL Server Database projects.
DAC files can only be published to a machine that has the SqlPackage.exe command installed. This should be
part of your existing SQL Server 2012 installation and is also available by installing SQL Server Database Tools
for Visual Studio.
Copyright (c) 2013 Brian Cowdery
Licensed under the MIT license.