On Thursday 06 July 2006 22:20, Linda Halligan wrote:
> Please don't beat me with the RTFM stick. I've searched for a few
> days now and I'm not able to find an answer to my question.
>
>
>
> I'm setting up a new subversion instance. It will contain a single
> repository with several projects. One of those projects is going to
> be the source for a tomcat based website. I want the website to get
> updated automatically only when the "website" project is updated.
> Since I'm not a coder I'm not entirely sure how to go about doing
> that.
>
>
>
> Is it possible to write a post-commit script that will execute only
> if that portion of the tree has been changed?
>
>
>
> If someone could point me to an example of how this could be done I
> would be eternally grateful.
Why use only one repository? If you have one repo per project,
requirements such as yours become much easier to handle. It is also
easier to maintain projects: Filtering a repo dump to remove bad
commit data, archiving and taking a project offline, mirroring a
specific project to another location, not taking all projects down if
there is repo corruption or other repo down time, etc....
From the client side, there is not much apparent difference between
one repo and many repos, but from an admin perspective, I can't see
much to recommend having only one repo. Unless you like writing
complex hook scripts ;-)
--
> Nick Thompson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 7 11:19:25 2006