Guten Tag Nick Stolwijk, am Dienstag, 14. Dezember 2010 um 12:03 schrieben Sie:
> Another easy one. ;) Using separate repositories for projects makes access control a lot easier and safer: Depending on using svnserve, one has the chance to use different instances for svnserve on different ports for different projects. We for example have divided our projects into source and binary projects, one for internal, one for internal and external use, with (nearly?) no chance that an external user can gain access to the internal repositories or any other port/service running on the svn-server. In one repository created users can't accidently gain access to repositories which they shouldn't get access on. Hooks can be managed on a per project base and you don't need to write UML for hooks just because you have 20 projects with different needs pre or post a commit. Maintenance if some problem occurs which needs dumping and loading or stuff like that is easier and faster. First page in WebSVN is descriptive to users out of the box. It's as always, if to decide what to centralize and what not... Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: tschoen...@am-soft.de Web: http://www.am-soft.de AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
