package git
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=f6c628e3628d25686cec4cdff8132f9433e95938bdcb43975778d28d33a0b077
sha512=779bdd7a1657e859ed47b46ef9da007b5f43f4446f8cea831f29fae662efdd33a39aa2ee90b9f8d8b6360f2abb78038a7592633efa26e8adc5d2ae20d86d8015
doc/smart_git/Smart_git/index.html
Module Smart_git
Source
Mimic values.
When the user use an Endpoint.t
to Make.fetch
or Make.push
, we fill the given Mimic's ctx
with some available informations such as:
- if we want to
Make.fetch
(`Rd
) orMake.push
(`Wr
) - the scheme/protocol that the user would like to use (
git://
, SSH or HTTP - with or without TLS) - the path of the git repository
- the host (an IP adress or a domain name)
- the SSH user iff the user would like to use SSH
- the port that the user would like to use
From this informations, the end-user can process them through the Mimic API (with Mimic.fold
) and describe how to create needed values to start a protocol from them.
For example, if the user wants to use mirage-tcpip
which needs an IP address and a port, he is able to re-use/map/fold git_host
and git_port
to craft what mirage-tcpip
really needs.
Of course, such job is definitely outside the scope of ocaml-git
and permits to us to be free about protocol implementations. An example of the plumbing needed is able with git-mirage
which re-use these values to be able to start a mirage-tcpip
connection, a awa-ssh
connection of a cohttp
(with or without ocaml-tls
) connection.