~aw/patches

2 2

Git Daemon question

Details
Message ID
<C9YF6VPQVE7O.1SOUVIXVFI69X@debian-alex>
DKIM signature
pass
Download raw message
Hey Johann, I had a quick question about one of your changes -- you
added the git-daemon file -- was your idea that the public clone URL
would be using a git url? I was thinking I would support https cloning
because it's simpler to set up (e.g. only requires 1 open port) -- what
do you think?

Alex
Johann Galle
Details
Message ID
<6EF6433C-BCAE-4B77-ABC3-FEFD59E458FB@qwertqwefsday.eu>
In-Reply-To
<C9YF6VPQVE7O.1SOUVIXVFI69X@debian-alex> (view parent)
DKIM signature
pass
Download raw message
I added that out of "convention" because gitweb also uses this, independently of the git daemon. There should probably be a config option to change the name of that file. Then setting the name to "." or some other file that is guaranteed to exist could be used to disable the check.
So this has nothing to do with using the git daemon or not.

Regarding that I would say that it's not really difficult to set up the git daemon, but if we included https cloning, probably not many people would bother to set it up, so it would be nice if we can do it. But still in theory that's completely independent, so "interoperability" would be nice.
Details
Message ID
<3F6B08E1-BA48-4B50-9F10-4A0F902F9E33@alexwennerberg.com>
In-Reply-To
<6EF6433C-BCAE-4B77-ABC3-FEFD59E458FB@qwertqwefsday.eu> (view parent)
DKIM signature
pass
Download raw message
Thanks, that makes sense! I did some research into the email side of things, seeing what Rust libraries exist, etc and I think I’m going to focus my energy this week on email stuff to see if i can work out an architecture i like andget something together

Alex

> On Mar 15, 2021, at 11:17 PM, Johann Galle <johann@qwertqwefsday.eu> wrote:
> 
> I added that out of "convention" because gitweb also uses this, independently of the git daemon. There should probably be a config option to change the name of that file. Then setting the name to "." or some other file that is guaranteed to exist could be used to disable the check.
> So this has nothing to do with using the git daemon or not.
> 
> Regarding that I would say that it's not really difficult to set up the git daemon, but if we included https cloning, probably not many people would bother to set it up, so it would be nice if we can do it. But still in theory that's completely independent, so "interoperability" would be nice.
Reply to thread Export thread (mbox)