git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Simon Phai <simonphaikm@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Server
Date: Thu, 4 Apr 2024 21:14:57 +0000	[thread overview]
Message-ID: <Zg8YUYSH2cSb7k6J@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CACArJ23dNONx-Fk5VwZZ+A64aEYW0nhn+X6q50W5hKLN=VbEng@mail.gmail.com>

[-- 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 --]

  reply	other threads:[~2024-04-04 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  9:54 Git Server Simon Phai
2024-04-04 10:08 ` Konstantin Khomoutov
2024-04-04 10:26   ` Simon Phai
2024-04-04 21:14     ` brian m. carlson [this message]
2024-04-05  9:11     ` Konstantin Khomoutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zg8YUYSH2cSb7k6J@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=simonphaikm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).