What are you using to deploy your script for complex server products?
What are you using to deploy your script for complex server products?
Imagine we have some kind of new new code (or maybe version 42 of the spotted code) and submit it. Now, of course, we have the fundamental principles - creating and modernizing databases. We have nice "packages" (zip files). But between "shiny new server" and "OK, now hit the" Move "button - from services to third-party software to fonts.
We are MS store, by the way: IIS, ASP.NET, MSSQL. We mainly deploy our own servers. As the product grows larger and scales horizontally, upgrading a large number of servers becomes difficult.
Enlighten me how to do this easily and well with an answer to any of the following ...
- What's your favorite server deployment solution?
- How often do you go back to manual steps (add this x to IIS)?
- Does anyone really use website customization projects in Visual Studio?
- Are you cheaper to buy an intern than a script?
- If you script this, what are you using - and did you like it? (Someone here just made a compelling installer from MSBUILD. After .NET - installs, it's always there.)
- Have you learned to love WMI? How?
- You have attained the transcendence of embedding. Does a glimpse of a shiny new server deploy the code and all its dependencies? How?
source to share
We use NAnt build files to build and package (zip) our projects. Powershell scripts deploy the package to target computers, including web applications and Windows services. RedGate SQL Compare / SQL Data Compare , written using PowerShell, to update database schemas and static data. All are managed by the JetBrain TeamCity continuous integration server .
The same scripts are used for deployment in our test, QA and production environments, and everything is of course kept in source control.
source to share
We use NANT to download new versions. We modified it according to our needs and it works fine. We hardly need to make any manual changes other than the manual changes to the web.config. We download a new version weekly and in some cases we download it daily. We have the option to go back to the previous version, we can choose which servers to load, we upload different branches to different servers, everything we needed to do we were able to build on top of it.
I recommend writing some kind of loading script. This is the best way to make sure you haven't forgotten anything, that you can lean back easily, and that you know exactly what is happening on your servers.
source to share