Git yana zaɓar dokokin SSH ta sunan da ke cikin URL ɗinsa na nesa
Yi amfani da laƙabin masarautar SSH a cikin URL ɗin Git na nesa domin a zaɓi Host block da ProxyCommand da ake so.
Yi amfani da laƙabin SSH a cikin Git remote lokacin da laƙabin ke da hanyar proxy:
Host code-via-proxy
HostName git.example.net
User git
ProxyCommand nc -X connect -x proxy.example.net:8080 %h %p
Ana kwatanta code-via-proxy da sunan SSH da aka bayar. Sannan HostName yana gano ainihin uwar garke. Misalin yana buƙatar netcat mai jituwa da OpenBSD: -X connect yana neman HTTP CONNECT zuwa wurin SSH.
Don sabon checkout:
git clone git@code-via-proxy:team/project.git
Don checkout da ke akwai:
git remote set-url origin git@code-via-proxy:team/project.git
Saka ainihin hanyar ajiyar bayanai. Laƙabin yana canza zaɓin haɗi, ba asalin ajiyar a kan uwar garkensa ba. Don uwar garken Git SSH na jama'a a cibiyar da ke ba da izinin mai shiga tsakani na jama'a, jerin proxy na HTTP yana ba da 'yan takara don masarautar proxy da tashar. Yi amfani da misalin da ba shi da asusun proxy kawai tare da node da ke ba da izinin CONNECT zuwa ainihin wurin SSH da tashar.
Remote da ke amfani da [email protected]:team/project.git yana dacewa da git.example.net maimakon. Ba ya zaɓar laƙabin don kawai HostName na laƙabin yana nuni zuwa nan. Ko yi amfani da laƙabin ko sanya dokar da ake so ƙarƙashin ainihin sunan.
Duba kuma tubalan da suka dace na baya. A yawancin zaɓuɓɓukan SSH ƙimar farko da aka samu ce ke nasara, don haka sanya takamaiman saituna kafin manyan tsoffin da ke bayyana wannan zaɓi.