New post
Question
· Apr 2

How configure GIT in LINUX

#Git #Key Question #Red Hat Enterprise Linux (RHEL) #Caché

Hello!

Trying to configure tortoise GIT in Linux System

NAME="Red Hat Enterprise Linux Server"
VERSION="7.9 (Maipo)"

My steps

1. Enable [write-access](http://docs.intersystems.com/ens20151/csp/docbook/DocBook.UI.Page.cls?KE...) to CACHELIB database via the Management Portal. (This is required for csp-page with settings import.)
2. Import project in %SYS:

    %SYS> do $system.OBJ.ImportDir("/arch/cache-tort-git-master/","*.xml","ck",,1)

3. Now you can disable write-access to CACHELIB.
4. In Management Portal select the new %SourceControl.Git class as the desired Source Control class in all namespaces where you wish to use it. (System Administration >> Configuration >> Additional Settings >> Source Control)

 

But in cache studio there are no options to work with git.

Product version: Caché 2017.1
$ZV: Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2017.2.2 (Build 867_4_20165U) Mon Aug 17 2020 11:28:28 EDT
Discussion (12)3
Log in or sign up to continue
Ben Spead · Apr 2

@Timothy Leavitt / @Pravin Barton - can you please weigh in on whether it is possible to run git-source-control on Caché 2017.1?  I know the atelier APIs are present in that version (in at least an early iteration) but are there other things missing which would prevent it from working?

@Token Ibragimov - curious, do you have a rough timeline as to when you'll be moving to InterSystems IRIS?

0 0
Ben Spead · Apr 2

@Token Ibragimov - is your intention to have only a single developer working on this Linux system, or will many developers be making changes?  The reason that I ask is that while there have historically been a number of Caché git source control hooks which have been created and discussed on this community (a search here will find several examples), they have all assumed the normal git way of working which is a single developer per environment.  This has caused challenges with the typical way of developing on InterSystems products, which is many developers against a single instance.  This is why my team created git-source-control, in order to make git available in a way that works more seamlessly with our products.  

If you are going to be stuck on Caché for a while, you may want to consider other source control options which are designed to work natively with the platform, like Deltanji (https://georgejames.com/deltanji/).

Let's see what Pravin and/or Tim think about git-source-control working against Caché 2017.1.

0 0
Timothy Leavitt · Apr 2

We'll be getting out the next release of git-source-control (https://github.com/intersystems/git-source-control) this month, which includes support back to 2016.2 via an artifact associated with (some) releases. We haven't produced this for the past few releases but will do so for the next one.

You can follow the project here to be notified about new releases: https://openexchange.intersystems.com/package/Git-for-Shared-Development...

1 0