StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>We've been hosting behind apache 2.0.x for a few years now and I've been nothing but happy with it. We are using <a href="http://sourceforge.net/projects/mod-auth-sspi" rel="nofollow noreferrer">mod_auth_sspi</a> for user authentication, <a href="http://svnbook.red-bean.com/en/1.5/svn.ref.mod_authz_svn.conf.html" rel="nofollow noreferrer">mod_authz_svn</a> for user/path authorization, and <a href="http://svnbook.red-bean.com/en/1.1/re58.html" rel="nofollow noreferrer">mod_dav_svn</a> to add in WebDAV access. Once you get it installed and configured, it just keeps working. It is really convenient to be able to browse the repository using WebDAV as well. If you need more, then you can install any one of the web viewer tools.</p> <p>The configuration was pretty easy as long as you can just give every authenticated user read access and then create user groups and grant write access to either complete repositories or subtrees. Separating authentication and access control makes the system really nice to maintain as users come and go. We are currently hosting three repositories on one Win2K server. We have somewhere around 50 or 60 total users and most of the access is concentrated on one of the repositories. The last time that I checked we had about 7 or 8 simultaneous connections and about 6GB total. I'm not sure what that calculates to in file size though.</p> <p>A few warnings are warranted...</p> <ol> <li>Read <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">Version Control with Subversion</a> a few times</li> <li>Figure out how you want to layout your repository before you start committing code</li> <li>Really make sure that you have thought out the repository layout... in particular how you are going to maintain multiple versions and branches.</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload