Sitefinity is a .Net Web application supporting a number of standard and state of the art technologies as .Net Membership, Claims, MVC, HTML5, JavaScript, JQuery etc… To function properly they each require specific configuration settings both at application level and machine level. Many companies develop with Sitefinity within a continuous development and delivery pipeline. Regularly deploying and updating Test, Infrastructure, Staging and Production servers consistently can be a somewhat tedious manual bunch of tasks.
Whether it is to automate your development pipeline, or just to ensure that correct configurations and deployments steps are executed, using Octopus Deploy with Sitefinity is both easy, and relatively quick to set up and run.
Octopus Deployment Octopus Deploy Server component let’s you define all your environments [Test, Acceptance, Staging…], configure deployment steps [IIS Configuration, Machine provisioning, Windows Services, Databases…], Order those steps and make a release [a collection of steps specific to one or more environments to be executed]. Octopus Deployment Release
The installation of Octopus components is extremely simple and just requires that you executed a setup.exe file on the server and on each client machine participating in your deployment. You can also further integrate Octopus Deploy with your Build Server, as Octopus has also deep integration with JetBrains Teamcity and TFS, and has a command line application for creating and deploying releases that can be integrated with any build server.
All you need to do is download the Octopus Server component and the Tentacle component (client). Get Nugget Package Explorer to create your nugget packages for DB and Web Application deployments. Install Octopus and get the Scripts you need from within the application or from the Script library of Octopus, alternatively you can create or customize any existing script.
CONCLUSION
Octopus, tentacles, squids are specialized in deployments, while an elephant never forgets, humans do. It’s easy to miss something with numerous deployment steps executed on multiple systems, while once you have configured and tested your deployment correctness with Octopus you can trigger it in a few clicks. The choice is yours.
Resource links: