Chris HoffmanHello,
Is there a distribution of the git server for Windows, or am I totally missing the point of git? Will a simple file share work, or do I have to worry about file locking and such (e.g., two people try to commit at the same time).
Thanks, Chris
Jakub NarebskiRe: git-daemon on Windows?
"Chris Hoffman" <chris.c.hoffman@gmail.com> writes:
> Is there a distribution of the git server for Windows, or am I totally > missing the point of git?
I don't know about git-daemon (git server) under Windows, but you can use I think any web server (Apache, lighttpd, or even IIS) can serve git over HTTP, and any web server with WebDAV can enable pushing to git repositories. Please remember that "dumb" protocols such as HTTP require additional info which must be generated by git (usually in post-update / post-commit hook), or transferred.
You can use SSH to access repositories, but I don't know any SSH server for Windows. You can use Cygwin OpenSSH server, I think (restrict access with git-shell, or use gitosis)...
Or you can use any networked file system.
> Will a simple file share work, or do I have to worry about file > locking and such (e.g., two people try to commit at the same time).
The preferred workflow is for each person to have its own clone of repository; one repository plays role of central one, ut not by socilogical not technical reasons. Centralized workflow is possible, but id doesn't take as much attention.
-- Jakub Narebski Poland ShadeHawk on #git
Avery PennarunRe: git-daemon on Windows?
On 6/11/08, Jakub Narebski <jnareb@gmail.com> wrote:
> "Chris Hoffman" <chris.c.hoffman@gmail.com> writes: > > > Is there a distribution of the git server for Windows, or am I totally > > missing the point of git? > > I don't know about git-daemon (git server) under Windows
I can confirm that the git-daemon works fine on Windows (cygwin). Currently using git 1.5.5, but previous versions worked for me as well.
But Jakub's other suggestions are probably more appropriate for a "git server" in the same sense as an "svn server" or "p4 server" (ie. read-write access with authentication).
Have fun,
Avery
Johannes SixtRe: git-daemon on Windows?
Chris Hoffman schrieb:
> Is there a distribution of the git server for Windows, or am I totally > missing the point of git? Will a simple file share work, or do I have > to worry about file locking and such (e.g., two people try to commit > at the same time).
You are missing *some* point of git: Usually, everyone has his own repository, hence, commits that happen concurrently won't be a problem.
But you must exchange your work, and for this it is common that everyone in addition has a publically accessible (bare) repository. These you can place on a normal file share. I do this all the time.
You *can* choose to have only a single (bare) repository that everyone uses to exchange work. But then you do have to worry about concurrent *pushes* that get in the way of each other. You have this problem no matter which form of server you chose (file share, ssh, git daemon, WebDAV). If you go this route, you need a policy how people publish their work (eg. branch namespaces). msysgit and 4msysgit do it this way.
-- Hannes
Re: git-daemon on Windows?
I'm trying to learn about this too. I found the gittutorial http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html useful. See the section "Using git for collaboration", which explains how use can use a shared filesystem.
Or maybe I don't understand the subtleties of the issue.
John.
On Wed, Jun 11, 2008 at 2:54 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Chris Hoffman schrieb: >> Is there a distribution of the git server for Windows, or am I totally >> missing the point of git? Will a simple file share work, or do I have >> to worry about file locking and such (e.g., two people try to commit >> at the same time). > > You are missing *some* point of git: Usually, everyone has his own > repository, hence, commits that happen concurrently won't be a problem. > > But you must exchange your work, and for this it is common that everyone > in addition has a publically accessible (bare) repository. These you can > place on a normal file share. I do this all the time. > > You *can* choose to have only a single (bare) repository that everyone > uses to exchange work. But then you do have to worry about concurrent > *pushes* that get in the way of each other. You have this problem no > matter which form of server you chose (file share, ssh, git daemon, > WebDAV). If you go this route, you need a policy how people publish their > work (eg. branch namespaces). msysgit and 4msysgit do it this way. > > -- Hannes > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
Chris HoffmanRe: git-daemon on Windows?
Yes, I think that this is a very good section of the tutorial to consult. It is just hard for me to beat back my subversion thinking.
On Thu, Jun 12, 2008 at 11:23 AM, John Yesberg <john.yesberg@gmail.com> wrote:
> I'm trying to learn about this too. > I found the gittutorial > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > useful. > See the section "Using git for collaboration", which explains how use > can use a shared filesystem. > > Or maybe I don't understand the subtleties of the issue. > > John. > > On Wed, Jun 11, 2008 at 2:54 PM, Johannes Sixt <j.sixt@viscovery.net> wrote: >> Chris Hoffman schrieb: >>> Is there a distribution of the git server for Windows, or am I totally >>> missing the point of git? Will a simple file share work, or do I have >>> to worry about file locking and such (e.g., two people try to commit >>> at the same time). >> >> You are missing *some* point of git: Usually, everyone has his own >> repository, hence, commits that happen concurrently won't be a problem. >> >> But you must exchange your work, and for this it is common that everyone >> in addition has a publically accessible (bare) repository. These you can >> place on a normal file share. I do this all the time. >> >> You *can* choose to have only a single (bare) repository that everyone >> uses to exchange work. But then you do have to worry about concurrent >> *pushes* that get in the way of each other. You have this problem no >> matter which form of server you chose (file share, ssh, git daemon, >> WebDAV). If you go this route, you need a policy how people publish their >> work (eg. branch namespaces). msysgit and 4msysgit do it this way. >> >> -- Hannes >> -- >> To unsubscribe from this list: send the line "unsubscribe git" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >