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

Re: Question re. git remote repository

From
KKKonstantin Khomoutov <kostix+git@007spb.ru>
Date
Jan 16, 2013, 18:06 UTC
Message-ID
<20130116220615.48c159546bccfa5b9cd9028e@domain007.com>
In-Reply-To
<201301161749.r0GHnGV6007806@smtpb02.one-mail.on.ca>

On Wed, 16 Jan 2013 17:49:09 +0000 "Lang, David" <David.Lang@uhn.ca> wrote:

Show 6 quoted lines
> We're just in the process of investigating a versioning tool and are
> very interesting in git. We have one question we're hoping someone
> can answer. In regards to the repositories, I think I understand
> correctly that each developer will have a local repository that they
> will work from, and that there will also be a remote repository
> (origin) that will hold the original version of the project.
The name "origin" is purely arbitrary: any local repository might have
> It appears from the limited reading I've done that the remote
> repository must be hosted at github.com. Is this the case?

Of course not. github is just a Git hosting provider. There are plenty of them -- both commercial and not-for-profit (a well-known service bitbucket.org is one example).

> Ideally we'd prefer to simply create our remote repository on a drive
> of one of our local network servers. Is this possible?

Yes, this is possible, but it's not advised to keep such a "reference" repository on an exported networked drive for a number of reasons (both performance and bug-free operation).

Instead, the canonical way to host "reference" repositories is to make them accessible via SSH or via HTTP[S]. To do this, a server running some POSIX OS (Linux- or *BSD-based) is the best bet. Both kinds of access require Git itself installed on the server. Obviously, SSH access requires an SSH server software (such as OpenSSH) as well and HTTP[S] access requires a web server (such as Apache). Of course, everything mentioned is available on any sensible OS you might install on your server. Read-only access might be provided by a special tool named "Git daemon" which is a part of Git.

If you have more than a couple of developers you might want to install certain front-end Git software on the server which provides for "virtualized" Git users and fine-grained control over who can do what. Using gitolite [3] for this is the current trend.

Web-browsing for your repositories, if needed, is usually provided by the tool named gitweb [4].

Everything I've just summarised is well explained in [5] and [6] (as an addendum).

Another approach is to set up a "turn-key" solution such as GitLab [1] or gitblit [2].

1. http://gitlabhq.com/
2. http://gitblit.com/
3. https://github.com/sitaramc/gitolite
4. https://git.wiki.kernel.org/index.php/Gitweb
5. http://git-scm.com/book/en/Git-on-the-Server
6. http://git-scm.com/2010/03/04/smart-http.html
Previous: Lang, DavidNext: Jeff King
Message 2 of 21 in “Question re. git remote repository”
  1. Lang, DavidJan 16, 2013
  2. Konstantin KhomoutovJan 16, 2013
  3. Jeff KingJan 16, 2013
  4. Konstantin KhomoutovJan 16, 2013
  5. Stephen SmithJan 16, 2013
  6. David LangJan 16, 2013
  7. Lang, DavidJan 17, 2013
  8. Matt SeitzJan 18, 2013
  9. David LangJan 18, 2013
  10. Lang, DavidJan 18, 2013
  11. Matt SeitzJan 18, 2013
  12. Lang, DavidJan 23, 2013
  13. Junio C HamanoJan 23, 2013
  14. Jeff KingJan 17, 2013
  15. David LangJan 16, 2013
  16. David LangJan 17, 2013
  17. David LangJan 18, 2013
  18. Junio C HamanoJan 18, 2013
  19. David LangJan 18, 2013
  20. Junio C HamanoJan 18, 2013
  21. Philip OakleyJan 18, 2013

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.