I came across an interesting question on Server Fault recently:

I’m doing svn update to update the code for my php website, but it leaves .svn/ folders all over.

I think its dangerous to leave those files publically readable, but its very easy to update the system.

Is there a way to use svn update to update the system, but not to export the .svn/ folders?

Solid answer, too.

I think most developers have experienced this at some point in their career, but I think that this supports the notion of spending a little bit of time hooking up your local, staging, and production environments to source control and deployment tooling.

Getting that stuff automated – as much pain as it can be to actually setup – makes testing and deploying so much easier.