CODEWITHSUNDEEP
iisdeployment
Sean Carpenter
Sean Carpenter

Reputation: 7721

What is a good deployment tool for websites on Windows?

I'm looking for something that can copy (preferably only changed) files from a development machine to a staging machine and finally to a set of production machines.

A "what if" mode would be nice as would the capability to "rollback" the last deployment. Database migrations aren't a necessary feature.

UPDATE: A free/low-cost tool would be great, but cost isn't the only concern. A tool that could actually manage deployment from one environment to the next (dev->staging->production instead of from a development machine to each environment) would also be ideal.

The other big nice-to-have is the ability to only copy changed files - some of our older sites contain hundreds of .asp files.

Upvotes: 9

Views: 2228

Answers (7)

januszstabik
januszstabik

Reputation: 1162

Try repliweb. It handles full rollback to previous versions of files. I've used it whilst working for a client who demanded its use and I;ve become a big fan of it, partiularily:

  • Rollback to previous versions of code
  • Authentication and rules for different user roles
  • Deploy to multiple environments
  • Full reporting to the user via email / logs statiing what has changed, what the current version is etc.

Upvotes: 0

projectshave
projectshave

Reputation: 4051

Maybe rsync plus some custom scripts will do the trick.

Upvotes: 0

Simon_Weaver
Simon_Weaver

Reputation: 145880

I've given up trying to find a good free product that works. I then found Microsoft's Sync Toy 2.0 which while lacking in options works well.

BUT I need to deploy to a remote server.

Since I connect with terminal services I realized I can select my local hard drive when I connect and then in explorer on the remote server i can open \\tsclient\S\MyWebsite on the remote server.

I then use synctoy with that path and synchronize it with my server. Seems to work pretty well and fast so far...

Upvotes: 0

splattne
splattne

Reputation: 104030

For some scenarios I used a freeware product called SyncBack (Download here).

It provides complex, multi-step file synchronization (filesystem or FTP etc., compression etc.). The program has a nice graphical user interface. You can define profiles and group/execute them together.

You can set filter on file types, names etc. and execute commands/programs after the job execution. There is also a job log provided as html report, which can be sent as email to you if you schedule the job.

There is also a professional version of the software, but for common tasks the freeware should do fine.

alt text

Upvotes: 2

DrFloyd5
DrFloyd5

Reputation: 13787

@Sean Carpenter can you tell us a little more about your environment? Should the solution be free? simple?

I find robocopy to be pretty slick for this sort of thing. Wrap in up in a batch file and you are good to go. It's a glorified xcopy, but deploying my website isn't really hard. Just copy out the files.

As far as rollbacks... You are using source control right? Just pull the old source out of there. Or, in your batch file, ALSO copy the deployment to another folder called website yyyy.mm.dd so you have a lovely folder ready to go in an emergency.

look at the for command for details on how to get the parts of the date.

robocopy.exe
for /?

Yeah, it's a total "hack" but it moves the files nicely.

Upvotes: 2

Guy Starbuck
Guy Starbuck

Reputation: 21873

You don't specify if you are using Visual Studio .NET, but there are a few built-in tools in Visual Studio 2005 and 2008:

Copy Website tool -- basically a visual synchronization tool, it highlights files and lets you copy from one to the other. Manual, built into Visual Studio.

aspnet_compiler.exe -- lets you precompile websites.

Of course you can create a web deployment package and deploy as an MSI as well.

I have used a combination of Cruise Control.NET, nant and MSBuild to compile, and swap out configuration files for specific environments and copy the files to a build output directory. Then we had another nant script to do the file copying (and run database scripts if necessary).

For a rollback, we would save all prior deployments, so theoretically rolling back just involved redeploying the last working build (and restoring the database).

Upvotes: 1

lomaxx
lomaxx

Reputation: 115763

We used UnleashIt (unfortunate name I know) which was nicely customizable and allowed you to save profiles for deploying to different servers. It also has a "backup" feature which will backup your production files before deployment so rollback should be pretty easy.

Upvotes: 0

Related Questions