> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of larry price > Sent: Thursday, June 01, 2006 12:56 AM > To: Eugene Unix and Gnu/Linux User Group > Subject: Re: [Eug-lug] subversion repository design > > On 5/31/06, Rob Hudson <[EMAIL PROTECTED]> wrote: > > > I like the one big repository model. We do that at Orcas and have > > subdirectories off that that for tags, trunk, or branches. > Under that > > we have department, the projects, etc... > > That's what I'm going with in this instance, it seems simpler > and more straight forward. > > > That's another decision you'll have to make... do you > prefer trunk/tag > > at the root or under each project? > > I have it set up at the root right now; up until now my use > of version control has been fairly primitive with basically a > growing tip, and a need to do occasional rollbacks. > > I am getting to the point where I want to have stable and > development branches for some subprojects. Having each > project set up with it's own trunk/branch/tags set makes a > lot of sense to me. Especially since I may need to split them > off onto separate machines/separate administrative domains at > some point in the future. > > > Would running multiple instances of Subversion on the same > server have > > implications for the ports? > > For now it's mostly me using svnserve -t I may have some > other people using it in the same way; but I don't foresee > needing a large scale solution.
If you really need multiple repositories on the same server, you'd probably want to use apache with DAV. http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html I have one server here that's web-testing/svn repository so I had Apache2 on it already, and it worked out well. I'm also using trac (http://trac.edgewall.com/) on the same server. Jason LaPier Network Manager TACS / WRRC / NPSO University of Oregon _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
