On 6/6/07, Lopez, Denise <dlopez@humnet.ucla.edu> wrote:
>
>
>
>
> Maybe I wasn't clear. We are going to use TortoiseSVN as a client to
> checkout and commit and browse the repositories. The repository in question
> is made up of php scripts and images that make up a website.
>
>
>
> We are using subversion because we have 3 or 4 developers for the website.
> So when a change gets committed to the repository how can I set it up so the
> website displays the changes. So I don't want to view the repository
> indexed files, I want to view the updated php scripts through Apache.
>
>
>
> Does this make more sense?
Yes - it's a completely different question from what most people
probably read your original post as.
What you want to do is to have a post-commit hook script which updates
the copy of the project which Apache serves. You can either make the
directory which Apache is serving a working copy, and run svn update
against it, or perform an export each time. The working copy will be
more efficient as far as updating goes (only changes will have to get
copied), but you'll want to restrict access to directories named .svn
via .htaccess or your httpd.conf.
This comes up pretty regularly on this list and other svn-related
discussion venues, a couple quick searches should turn up previous
discussion.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 6 21:24:31 2007