ASP.NET网站项目，Mercurial / Git，部署 - 一种简单的方法？

Question

We have a small team of two developers (PC) and two designers (Mac). As we're an ad agency rather than a code shop we don't get to spend lots on software tools. We used to use Visual Studio years ago but now we use Visual Web Developer to create ASP.NET sites (.NET4 support - can't afford new VS licences). We create the sites as Web Site projects (rather than Web Apps, or MVC) and we run on a dedicated dev box (Win 2008 rc2 server).

TortoiseHg is the latest I've been playing with and the difference between Hg and Git are negligibility considering our needs. So we can run with either.

What I'm trying to do is find a relatively simple way of deploying sites/commits using freely available tools/services that works well with the tech/software that we use.

I don't mind lots of faffing to set up the solution if it can be setup up once on say one of our server but could deploy to multiple locations. I've been looking and CI server (Jenkins/Hudson) but they seem to be overkill for what we require. Do we need a build server for a 50 off web pages and associated assets?

I tried the Mercurial HgWebDir setup thing - too many potential problems with Hg/Python versions and the setup time is too long per production server - I had to download the source, make a change and rebuild it... OTT. Git seems to work best with SSH, again, more 3rd party stuff.

Is there any Windows based software that we can install on the production server or on a central server that will aid with simple deployment (ie copy latest changes to website directory and rollback) that doesn't cost the earth (preferably free) and doesn't rely on getting the right versions of this and that to work properly.

Answer 1

Let's imagine that you have choosen AppHarbor for your .NET hosting.

They give you a GIT repository where you can have your source code and upon each push to appharbor they will automatically build your solution and make it available online.

With this in mind, you can have a branch to be your production and everything else to help and to be used to host the source code and help files for example.

If you choose a hosting company that only provide you with an FTP upload feature, either you use a automatic script to publish the data from your commit (using webhooks you can easily fire a web script that will pick up the changes (or the entire repo) and publish on the web).

Either way is good, it's always up to you, what are you guys willing to try, and keep trying alternatives until all of you are happy with the result.

With this, you can simply use Visual Studio and Tortoise GIT or even install GIT Extension in Visual Studio and use no more software...

Using Git with Visual Studio

Answer 2

If deploying sites for you is "copy files from A to B" (no related build-process), you can try at least two methods, both assume the presence of working http-server on the "other" side

1. Export from repository to unversioned tree, full clean-up of webspace, copy new files into site
   • light-version of this solution: export only affected by changeset-range files and copy over old versions
2. Site-space is part of working copy (I prefer to see repo outside the web-root), update of working copy (pull from somerepo ) updates files on site

Only VCS + FTP|SCP|? clients used

Answer 3

Have you considered using WebMatrix for development? It helps streamline the process for small web sites like you describe.

CI is still useful for small projects, especially if you use unit tests. Using Hudson in small Teams

You should be able to use git to deploy to your server and rollback quite easily. You could create a bare git repository on your server and then use the post-receive git hook to automatically deploy the changes. So when you push changes to origin from your local repository, the website will be updated.