allura:db/5424 This leaves it in a dev/test configuration with no authentication, since that's is the tricky part. We can add that in with the [#6701] script.
--- ** [tickets:#5424] Provide instructions for running git/hg/svn services** **Status:** code-review **Labels:** docs **Created:** Thu Dec 06, 2012 01:29 AM UTC by Dave Brondsema **Last Updated:** Fri Dec 13, 2013 06:54 PM UTC **Owner:** Dave Brondsema For someone deploying Allura, they are left on their own to provide the git, hg, or svn services. We have some docs at http://allura.sourceforge.net/docs/scm_host.html about deploying ldap & fuse controls to SCM dirs, but nothing about running the scm services Gitlab (an OSS "competitor" to Allura) includes Gitolite setup in their docs https://github.com/gitlabhq/gitlabhq/blob/stable/doc/install/installation.md --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
