[ome-devel] Woolz

[Curtis Rueden]

Hi Bill,

I'm looking at moving Woolz to git rather than cvs, something
> that's long overdue. Github seems the obvious choice for a
> public repository, but I'm keen to keep a git server internally
> too. What git servers can you recommend? I'm looking at
> gitosis/gitolite with a gitweb frontend. Any advise you can
> give here would be useful, as my only git experience is pulling
> stuff.
>

I agree that Github is awesome, and would definitely recommend using it. It
is *much* easier to administer (i.e., you don't have to) than a privately
maintained Git server. The downside is that if you want a non-public
repository, you have to pay them.

Anyway, LOCI runs our own Git server using gitosis, and it works very well.
The canonical setup article for that is:

http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way

The general idea is to use gitosis over SSH for read/write access, and
gitserve (i.e., "git://" protocol) for read-only public access.

It should be pretty straightforward to get working, though there is some
amount of pain involved. We use Ubuntu for our servers and it works pretty
well—in particular, it's pretty easy to find online support for
Ubuntu-based setups. If you do go that route, my advise is to read the
README.Debian.gz that often comes bundled with various packages, as it has
distro-specific notes about how that particular tool was configured to work
with Debian/Ubuntu (which sometimes differs from the general documentation
in surprising ways).

One cool thing about Git is that you can easily have multiple mirrors. The
tricky part is keeping them in sync. For that I recommend this (recently
completed) script written by Johannes Schindelin:

http://fiji.sc/cgi-bin/gitweb.cgi?p=fiji.git;a=blob;f=bin/git-synchronizer.sh;hb=refs/heads/master

Using that script, you can keep your Github repo synced with your private
one.

-Curtis

On Wed, Feb 22, 2012 at 10:07 AM, Bill Hill <Bill.Hill at igmm.ed.ac.uk> wrote:

> Thanks for all the useful information and advise at the meeting
> last week.
>
> I'm in the process of getting our Woolz imaging library into a
> nice clean state with new text for the copyright (now University
> of Edinburgh, was Medical Research Council) and license (remains
> GPL v2). I've built up quite a lot of changes recently so it may
> take until the end of the week for to get all this checked into
> our CVS repository. Once it's in I'll post the URL of a tarball
> with the current build and some brief build instructions for
> anyone that wants to take a look.
>
> I'm looking at moving Woolz to git rather than cvs, something
> that's long overdue. Github seems the obvious choice for a
> public repository, but I'm keen to keep a git server internally
> too. What git servers can you recommend? I'm looking at
> gitosis/gitolite with a gitweb frontend. Any advise you can
> give here would be useful, as my only git experience is pulling
> stuff.
>
> Cheers,
> Bill
> --
> Bill Hill                              : http://www.hgu.mrc.ac.uk
> MRC Human Genetics Unit                : http://www.emouseatlas.org
> MRC IGMM, University of Edinburgh      : Bill.Hill at igmm.ed.ac.uk
> Western General Hospital               : +44-131-3322471x4038
> Crewe Road, Edinburgh EH4 2XU, UK.     : +44-131-4678456
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
> ______________________________**_________________
> ome-devel mailing list
> ome-devel at lists.**openmicroscopy.org.uk<ome-devel at lists.openmicroscopy.org.uk>
> http://lists.openmicroscopy.**org.uk/mailman/listinfo/ome-**devel<http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20120222/852c0477/attachment.html>