Stop assuming implicit HTTPS about caddy-git HOT 6 CLOSED

It is actually the intended behaviour and there is no problem.

Which is not the indented behavior, as I'm expecting it to pull via SSH. Doing this way apparently fixes the problem:

I noticed Git tries to authenticate even for public repositories when using SSH, so I chose to do the transformation to HTTPS on the fly and use it instead.

May I know why you need SSH for public repository ?
Though I will close this issue because this behaviour does not yield different result for the user and it is intended.

from caddy-git.

I'm actually using a private repository, but I don't need to necessarily specify the SSH key if I have it on ~/.ssh/id_rsa, git seems to assume that by default. That's why I didn't want to specify a key and use the simple one-liner directive.
When people go to clone a GitHub repository, GitHub automatically gives them the HTTPS link by default:

For that reason I think the transformation to HTTPS is unneeded. And in my case, it results in unintended behavior :P

from caddy-git.

Bear in mind that it is implemented to be as standalone as possible. Imagine running it in a container or not having ssh keys configured. That is why you need the key specified.

I choose not to believe that additional curly braces and an extra line is that much of deal.

from caddy-git.

Fair enough 👍

I didn't want to specify the key due to another issue, it couldn't find my key at all:

Warning: Identity file .ssh/id_rsa not accessible: No such file or directory.

But that's another issue that I will hopefully fix. Removing the key parameter seemed like a quick option to remove that warning, but I noticed the middleware put "https://" before my Git SSH url, that's why I opened this issue.

from caddy-git.

Specify absolute path for key.

from caddy-git.

That solved it, thanks!

from caddy-git.