Hi, we are thinking of implementing a git repository for a group of end users for use with Enterprise Guide. The problem is - we are using a Linux server (9.4M3 running Data Management) and I'm uncertain of what our options are for deplyoment - would the Git repository have to be on the server itself? It would be used by a specific group of users and would be needed for audit purposes. We are using Enterprise Guide 7.1 running on Windows 7 desktops.
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
Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF
View now: on-demand content for SAS users
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
Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF
View now: on-demand content for SAS users
Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.
Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.