On 6/18/07, David Gardner <jgg.lists@gmail.com> wrote:
> I kinda have a similar situation where I'm going to be the primary web
> developer for a company that has a dedicated web server (win 2003
> box).
>
> I was planning on putting SVN on that server to version control my
> ColdFusion and HTML files.
>
> So what I'll end up with is my repository on the server, and then I'll
> also need another copy that goes into the web root, which is where the
> site is published.
>
> Idea 1: My friend said that perhaps I could have the web root be a
> checked out version of the repo. So after I committed my changes from
> my remote computer into the repo, I would do an Update on the web root
> so that it would sync up with the repo. But this would put hidden
> ".svn" folders in my web root structure (maybe that is bad, I don't
> know). And I don't really knowwhat other ramifications this would
> have since I'm kinda new to SVN.
This is a very common usage. Configure the web server to not serve (or
redirect to a 404 page) directories named .svn and you're all set.
This is pretty easy w/ IIS and Apache.
> Idea 2: Do some kind of Export from the repo to the web root. But I
> wonder if I can do an Export of only the latest changes and not the
> whole site.
Export is all or nothing. There isn't an incremental export, as
there's no information in the exported copy indicating where it came
from.
A third option is to have a working copy which is updated, and then
use rsync to publish the changes to your web root, telling rsync to
ignore .svn directories. But this really just adds another moving part
to the system, and if you can configure the server itself to not serve
.svn directories, idea 1 is ideal.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Jun 18 15:42:16 2007