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

Re: [PATCH 0/3] [RFC] Support for publishing projects at central site

From
Petr Baudis <pasky@suse.cz>
Date
Sep 25, 2008, 10:24 UTC
Message-ID
<20080925102447.GG10360@machine.or.cz>
In-Reply-To
<Pine.LNX.4.64.0809250951090.5683@ds9.cixit.se>
Hi!
On Thu, Sep 25, 2008 at 09:56:18AM +0100, Peter Krefting wrote:
Show 11 quoted lines
> pasky@suse.cz:
> 
> > This is not really meant for as-is application, of course, but more
> > to see if people think it is good idea to have this kind of
> > functionality in git-gui at all and how generic it should be. This
> > mini-series depends on pretty much all the other patches I have
> > submitted tonight.
> 
> As long as it is easy to implement the server-side back-end needed to
> automatically accept projects that you publish through this hook, then
> this is something that would really help out in this conext.

Well, the example URL points to a Girocco script - Girocco is cleaned up and modernized version of the repo.or.cz duct tape, that should be easy to reconfigure for any kind of deployment and then simply make install-able. But any kind of CGI script can be in principle hooked up to this, so you can just write short shell thing that will do the magic and then

	echo -e 'Content-type: text/plain\n\nRegistration succeeded!'
Show 6 quoted lines
> I currently need to perform some "magic" on the server-side to set up
> new projects, it would be nice if all the people using it have to do is
> to select a menu option saying "publish". Preferrably through the git
> protocol, so that I don't have to set up ssh on people's machines
> (working in a Windows environment here, so all central repositories are
> set up to use the git protocol for both pull and push).

Which protocol do you use does not really matter, just set up the locators right (or don't use them if you don't want to). I ended up using samba exports mapped to Windows drives, but just using the git protocol might make more sense in many scenarios.

> How do you envision discovering the location to publish to? Some kind
> of automatic configuration option would be nice. Perhaps be able to
> point git gui at some magic URI that would download an XML (or text)
> file describing the central server, perhaps?

I provide customized MSysGit package with tweaked installer and with custom /etc/gitconfig. I think in these deployments there is either this possibility or the machines are centrally administrated so the sysadmin can adjust /etc/gitconfigs.

-- 
				Petr "Pasky" Baudis
People who take cold baths never have rheumatism, but they have
cold baths.
Previous: Peter Krefting
Message 7 of 7 in “[RFC] Support for publishing projects at central site”
  1. 0/3 [RFC] Support for publishing projects at central sitepasky@suse.cz, Sep 24, 2008
  2. 1/3 git web--browse: Add --stdin option supportpasky@suse.cz, Sep 24, 2008
  3. 2/3 git-gui: Use git web--browse --stdin for safe URL passingpasky@suse.cz, Sep 24, 2008
  4. 3/3 [FYI]git-gui: repo.or.cz-ish fork integrationpasky@suse.cz, Sep 24, 2008
  5. Andreas EricssonSep 25, 2008
  6. Peter KreftingSep 25, 2008
  7. Petr BaudisSep 25, 2008

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.