Hi @newtolinux,
Your remote "origin" Git repository can exist wherever you like (on any platform Git is supported... ex. Linux, Windows, Max OS X, Solaris). It is also independent of your SAS server, so it does not have to be on the same machine.
The confusion usually stems when folks want to access their programs in EG through the SAS server (ex. SASApp->Files) (rather than opening them via the local file system) *AND* use Git. This scenario is not supported, because of the inherent way that Git works. EG needs direct file system access to the working Git repository (which it doesn't have when opening programs via the SAS server).
So, if you wish to use Git with external SAS programs, you should open those programs in EG from locally cloned Git repositories (accessible from your local file system).
For example... with Git, each user clones the remote (ex. "origin") repository to their local file system. Then, they work out of their locally cloned repository (ex. open .sas programs in EG, edit, and save them). When ready, they commit changes to their local repository. And finally, when ready to "publish" those changes to "the rest of the world" (back to the remote "origin", from which others clone, pull, and push), the user pushes their commits back to the remote "origin" repository.
Here is a paper on the Program History feature in EG, which may provide some additional understanding:
http://support.sas.com/resources/papers/proceedings14/SAS179-2014.pdf
Casey
... View more