On Fri, 27 Aug 2004 03:31:22 -0600, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > based on what i have read about it (which is basically everything i know > about :P), the apache route is more difficult to setup. if you are aiming > for administration experience i guess this is more worthwhile for you.
Not at all. I've set it up on our box, and everything's peachy. :) Of course, YMMV. If you're distro already has precompiled packages, that takes away a whole lot of the pain. What I noticed though is the planning out of the access to the repository (i.e. security.) Unlike with a svnserve+ssh setup, you really have to either setup Apache + mod_auth_pam + some PAM-based authentication, or manually manage users via htpasswd and its ilk. However, access control can be more fine-grained than svnserve+ssh-- you can limit users to r/o or r/w access *per repository directory*. As for svnserve+ssh working with mod_dav_svn? Haven't tried it myself. :) -- JM Ibanez - A million monkeys can't go wrong... http://www.livejournal.com/~jmibanez/ http://www.mycgiserver.com/~butiki/ -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
