How do you setup SVN for general website development/deployment?

This is for general websites development (LAMP Stack), not necessarily web applications though.

I'm just trying to setup some version control for client websites im building. Just trying to figure out the best way -- well how to do this...

I don't know how to setup SVN on my server. Do I have to do an additional step to push what's in trunk t开发者_如何学运维o the directory that the domain uses?

Noob alert: I have an idea of what Im trying to do but if I'm not giving enough details let me know I'll update..

I keep development and production environments separate; that is, the server never uses a working copy.

Edit for clarification: By "sever never uses a working copy" I mean that the "svn checkout" is never executed on the server and thus there is no WC located on the server. Instead the "svn export" command can used to "pull a revision" without creating a WC.

However, sometimes it is easy to pull (a specific tested tag) onto a server. So, as a transport mechanism, SVN is sometimes handy.

No. You should build WAR file, probably save it into something like Maven repo and then deploy that. Now - I'm talking J2EE I don't really know which technology you have in mind. But anyway - SVN is for your source code and resources, not for executable code. Plus - trunk is for your latest code (development) you probably want to create a release branch for production deployment

OK. LAMP. I would still use some sort of publishing to move files from SVN to wherever you want to deploy it. Ant, Maven - something like that. It's generally not a good idea to map your SVN repo to your webserver, you want to keep distro and source separate. Said that - the folder structure can be identical