Guten Tag Peter@locotel, am Mittwoch, 13. April 2011 um 13:30 schrieben Sie:
> The issue is that svn is not adapted to support web applications that > live under > web-servers. You can use it pretty fine this way, I do for Perl web applications processed by Apache HTTPD, Java web applications under Tomcat etc. > You have to export from repository to the web directory > every so > often to update the operational site (no checkin). You don't have to, the web applications in productional state are just tags in the repository and checked out as normal working copies directly in /var/www/whatever. Development is merged to the those tags whenever you think it's finde to do so and you just have to issue an svn update on the working copy on the server. > Also web-applications > can easily > live, be developed and tested on developers workstations. That's what trunk and/or branches are for, depending on the development model you prefer. > I found that having a WC being the same as /var/www/wc was unproductive > as a lot > of the svn files were deleted by the developers during debugging. Depends on their debugging and what is needed. Do they really need to delete whole directories this often? > So I > had to resort > to a way of managing revisions centrally and allow for a loose > development management > depending on individual preferences. Subversion will be of no use in this case or what are the features Subversion provides you will want to use? The logs won't be meaningful to you because whoever commits won't know all changes. Every commit will be huge and hard to look for errors etc. I don't think it's worth the time. 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
