Return-Path: X-Original-To: apmail-allura-users-archive@www.apache.org Delivered-To: apmail-allura-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1807110337 for ; Fri, 13 Feb 2015 19:09:21 +0000 (UTC) Received: (qmail 72685 invoked by uid 500); 13 Feb 2015 19:09:21 -0000 Delivered-To: apmail-allura-users-archive@allura.apache.org Received: (qmail 72660 invoked by uid 500); 13 Feb 2015 19:09:21 -0000 Mailing-List: contact users-help@allura.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@allura.apache.org Delivered-To: mailing list users@allura.apache.org Received: (qmail 72650 invoked by uid 99); 13 Feb 2015 19:09:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 19:09:20 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dave@brondsema.net designates 173.255.226.50 as permitted sender) Received: from [173.255.226.50] (HELO mail2.brondsema.net) (173.255.226.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 19:08:56 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: brondsem) by mail2.brondsema.net (Postfix) with ESMTPSA id 16A9AE270 for ; Fri, 13 Feb 2015 19:07:53 +0000 (UTC) Message-ID: <54DE4B81.7080108@brondsema.net> Date: Fri, 13 Feb 2015 14:07:45 -0500 From: Dave Brondsema MIME-Version: 1.0 To: users@allura.apache.org Subject: Re: Setting up Allura with an existing gitolite repository References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I haven't done it before (or heard of anyone using them together) but it should be possible since Allura runs separately from the actual git service. Integrating them together then, is where you'll have to do some configuration/customization. https://forge-allura.apache.org/docs/scm_host.html covers how to set it up with "plain" git and hopefully provides enough pointers that you can translate to work with gitolite. In short, the main points of integration are filesystem location (so Allura can show the repos, and make new repos), and users & permissions. If you have success or any questions, do share! -Dave On 2/12/15 2:22 PM, Philip Tait wrote: > Does anyone have any guidance on this? Any special changes needed, different > from a standard Git setup? > > -- > Philip J. Tait > http://subarutelescope.org -- Dave Brondsema : dave@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><