I usually just write here so I can remember these things later, but this time is something to be found by others.<\/p>\n\n\n\n
So, it is normal to have our git repositories accessible in the public internet (access controlled or not), but it is possible that your repositories are only accessible within your corporate network, and you would need to be inside the company or use a VPN to be able to use it.<\/p>\n\n\n\n
One of the ways that this can be circumvented is to use a port forward with an SSH connection, when updating some web app in an outside development environment, for example.<\/p>\n\n\n\n
Port forward is straightforward:<\/p>\n\n\n\n
ssh user@remote_host -R 10443:git.company.com:443<\/pre>\n\n\n\nthis will listen for local requests to port
10443<\/code> insideremote_host<\/code> and redirect them trough the SSH connection togit.company.com:443<\/code>. <\/p>\n\n\n\nThis way it should be easy to clone, pull and push directly to the centralized repository<\/p>\n\n\n\n
git clone https:\/\/localhost:10443\/path_to\/repository.git<\/pre>\n\n\n\nAnd that’s it.<\/p>\n\n\n\n
Of course you will need to be using a computer that is able to access the repository, either from inside or using a VPN, but the development environment does not need to.<\/p>\n\n\n\n
In time, maybe check with the company’s IT department if it’s OK to do this! \ud83d\ude09<\/p>\n\n\n\n
Hope this is useful for someone!<\/p>\n","protected":false},"excerpt":{"rendered":"
I usually just write here so I can remember these things later, but this time is something to be found by others. So, it is normal to have our git repositories accessible in the public internet (access controlled or not), but it is possible that your repositories are only accessible within your corporate network, and … <\/p>\n