Quote:
getting data off of a network repository is knowledge I have yet to stumble upon
Often the problem with getting the data from a remote repository is that you don't know enough about the "remote location" itself. For this, you would need help from your network admin, not a Git geek. :-) No, no, don't go, hear me at least...
The thing is that you can run a
git clone
command to "fetch" (not the
git fetch
[
^]) any repository that has Git initialized. The
git init
[
^] is a different thing, but to fetch a remote repository,
git clone
[
^] is best.
For example, let's try this Google's repository:
Guava[
^].
$ git clone https://github.com/google/guava orange
Try and run this command, you would see that Git would start downloading the Git contents (tree, history, etc. etc.) and put them under "orange" folder (this can be anything, you name it).
Quote:
I assumed that typiing a "git clone..." command would have copied all of the files on the blah-blah server over.
And you're not wrong. The problem would be, that the blah-blah server might just not allow everyone to copy the content. Many organizations use firewalls, network traffic controls, IP-blocking, and other techniques to prevent Internet users from accessing and copying the content; even with Git. I have used Namecheap as my domain provider for years and have hated their hosting services as they require SSH connections before I can run any command; so I would create an SSH connection, then run the commands from the window that is authenticated for the SSH tunneling, and... yeah, it's a mouthful, right?
Perhaps, you require an SSL certificate (even a self-signed one), or you need to connect to a proper VPN channel to communicate, or your Git requires credentials. Who knows? The best bet is, that when you try to run
git clone ...
, see what the response is. Normally, Git would render a response for failure or success. In any case, communicate this with the network administrator, or request access from an admin.
Good luck.