* Re: Git Server
2024-04-04 10:26 ` Simon Phai
@ 2024-04-04 21:14 ` brian m. carlson
2024-04-05 9:11 ` Konstantin Khomoutov
1 sibling, 0 replies; 5+ messages in thread
From: brian m. carlson @ 2024-04-04 21:14 UTC (permalink / raw)
To: Simon Phai; +Cc: git
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On 2024-04-04 at 10:26:31, Simon Phai wrote:
> actually I'm quite new to this but I would like to setup my own git
> server so that my fellows can develop our own repository, I find
> online there isn't much guide on using windows server to do it.
It's probably true that there's little documentation on hosting a Git
server on Windows because most people doing so on their own do it on
Linux or another Unix system. It certainly is possible, but because
it's a rather uncommon configuration, you'll typically be left to
figuring it out for yourself.
If you're using a Unix system, there are options like Gitolite and
Forgejo, depending on what you're looking for, but I'm unsure if any of
those support Windows. Running such a tool may be easier than doing it
yourself, but you may find that the documentation in `git http-backend
--help` may help you set up Git with an HTTP server (such as Apache) if
you're interested in doing that.
[Also, it's polite on this list to reply inline instead of on top with
everything quoted underneath.]
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Git Server
2024-04-04 10:26 ` Simon Phai
2024-04-04 21:14 ` brian m. carlson
@ 2024-04-05 9:11 ` Konstantin Khomoutov
1 sibling, 0 replies; 5+ messages in thread
From: Konstantin Khomoutov @ 2024-04-05 9:11 UTC (permalink / raw)
To: Simon Phai; +Cc: git
(Reformatted to have inline style [1].)
On Thu, Apr 04, 2024 at 06:26:31PM +0800, Simon Phai wrote:
> > > I want to host my own git server, may I understand the server OS can
> > > it be windows?
> >
> > Yes.
> >
> > But note that there exist quite many ways to "host a Git server", so you
> > should maybe explore what's already there and specify your requirements
> > more precisely.
> >
> > In the simplest form (if we forget about just running git-daemon in a
> > console window - providing unprotected R/O access to a given repository),
> > you either set up Git to be accessible via an SSH server or via a web
> > server (IIS works).
> >
> actually I'm quite new to this but I would like to setup my own git
> server so that my fellows can develop our own repository, I find
> online there isn't much guide on using windows server to do it.
Unfortunately, this added not too much information to the original question.
I mean, now we know that you want to host a Git server on a Windows system,
there is a single repository to make access to and that there is going to be
more than a single person to have access to that repository.
OK, let us try to maybe move a bit further.
The first thing to know, is that Git does not provide any "high-level" -
Github-like or GitLab-like, is you want - solution out of the box.
It basically provides three ways to access Git repositories remotely:
- A thing called "git-daemon" which provides an unprotected and
unauthenticated access to a Git repository. Because of these properties,
by default the access it read-only, and even though you can convince it
to be read-write, it's a bad idea unless you really understand what you're
doing, and, based on what you described about your prospective setup,
this is certainly not what you want to do.
- Two low-level programs (whose names do not matter) which are supposed to be
used in conjunction with an SSH client and server. This means you need to
have an SSH server running on the host with a Git repository (or multiple
repositories), and the clients are to use SSH clients to access those
repositories. For clients, this happens almost transparently - they do not
need to manually run SSH clients, it's done by "git push/fetch/pull"
commands automatically when the URL of a remote repo has the "ssh://"
scheme, - but the server-side setup has to be rather explicit.
- More low-level commands intended to serve access to Git repos with the help
of an HTTP server. This works in a manner quite similar to that of SSH,
just HTTP (these days, HTTPS is more common) transport is used instead.
Again, clients handle this automatically if the URL of a remote repository
to work with has the "http://" or "https://" schemes.
Note that neither of the described solutions provide any user management and
access control facilities, and this is arguably the most complex part of
setting server-side Git up: making an SSH or HTTP server start Git is not too
complex, but putting up user management and access control is harder, and is
different for SSH and HTTP.
To research, you could start with [2] and [3]. These do not present the whole
solutions but at least it's something you can probably start with.
Also note that having an SSH+Git and/or HTTP+Git combo only allows you to
maintain a so-called "rendez-vouz" repository (or a set of them) basically
used by a team to share their developments. Such a solution won't provide you
with a web-browsable access to repositories, code review, issue tracker and so
on and so forth. There will also be quite limited, if any, access to
fine-grained access control - basically to who can push where. If you need
anything of the above, you might have better luck trying a "turn-key" solution
such as [4] or [5].
1. https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
2. https://github.com/PowerShell/Win32-OpenSSH/wiki/Setting-up-a-Git-server-on-Windows-using-Git-for-Windows-and-Win32_OpenSSH
3. https://smalltech.com.au/blog/how-to-run-a-git-server-on-windows-with-iis
4. https://about.gitea.com/products/gitea/
5. https://gogs.io
^ permalink raw reply [flat|nested] 5+ messages in thread