Workflow for Small Web Projects?

We currently use Vault with Visual Studio for large ASP.Net
projects, and we'd like to begin using it for small web
projects, but are uncertain how to incorporate it into our
workflow. 

By small web projects, I mean the following: 3-5 developers,
a development server where the web site lives (a PHP site in
this case). Developers download files from the site via FTP
to work on them, and upload them when they're done. That's
it. There are no daily builds or, indeed, builds of any
kind, and developers often can't view their changes locally;
they have to upload back to the server to test. Development
lasts only 6-8 weeks before the site is handed off to the
client.

Ideally, source control in this context would work like
this: a developer checks out a file from the repository. He
works on it locally, occasionally uploading it to the
development site to test his changes, and when he's done, he
initiates a single action that both uploads the file to an
FTP server and checks it back into the repository. 

I guess what I'm saying is that I want Vault to
automatically copy files to an FTP server on check in.

We've tried Dreamweaver's limited source control features,
which approximates the above scenario. But it's extremely
flaky, and obviously lacks 99% of Vault's capabilities.

Has anyone used Vault for projects like this? Any ideas on
how one could?

Michael