git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] teamGIT bonjour support

From
Ben Hoskings <ben@hoskings.net>
Date
Aug 28, 2009, 10:06 UTC
Message-ID
<47ECFDB7-4189-4573-BC27-685603780F27@hoskings.net>
In-Reply-To
<2fcfa6df0908280002y221a22e6md27db56865472144@mail.gmail.com>
On 28/08/2009, at 5:02 PM, Abhijit Bhopatkar wrote:
Show 10 quoted lines
> I plan to do this on LAN using bonjour service discovery, and rest
> completely being handled inside teamGIT running as a daemon(may be in
> widely abused systray?). (Git will handle actual fetch/conflict
> checking etc.)
> On a side note i also plan to generate daily reports and configurable
> notifications.
>
> So I ask you people, is there a solution already cooking someplace?
> may be something i can integrate with teamGIT? (e.g. bonjour plugin
> for git dameon)

You should check out bananajour, it sounds like it might fight the bill quite nicely:

http://github.com/toolmantim/bananajour

Written by Tim Lucas, and hacked on by a bunch of us at the Gold Coast, Australia Railscamp in May: http://railscamps.com/

The idea is that for each repo you want to publish, bananajour creates and looks after a locally stored remote, that you push to ("git push banana master") to publish your work over bonjour.

There's also a web interface at your-machine.local:9331 which shows the other bananas that were found (via bonjour) on the network. ['9331' is for 'peel' :) ]

I'm not sure what the state of Linux support is, since most of us run OS X, but I'm pretty sure someone was working on Linux/zeroconf support.

Cheers Ben Hoskings

Previous: Abhijit BhopatkarNext: Ben Hoskings
Message 4 of 10 in “[RFC] teamGIT bonjour support”
  1. Abhijit BhopatkarAug 28, 2009
  2. John TapsellAug 28, 2009
  3. Abhijit BhopatkarAug 28, 2009
  4. Ben HoskingsAug 28, 2009
  5. Ben HoskingsAug 28, 2009
  6. Jakub NarebskiAug 28, 2009
  7. Abhijit BhopatkarAug 28, 2009
  8. Petr BaudisNov 20, 2009
  9. Petr BaudisNov 20, 2009
  10. Björn SteinbrinkNov 20, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.