go to post Ben Spead · Feb 3, 2022 In the \bin directory is the csystray.exe file. Run that to get the cube running. Alternatively, you can use the cube that you do see in your systray and select "Remote System Access" to get to Studio, SMP, etc of your second instance.
go to post Ben Spead · Feb 3, 2022 No idea, but I don't think it's tied to the IRIS name. When I am logged into Studio as bspead I see the following: [quote] w ##class(%SYSTEM.Util).GetEnviron("USER")rootw ##class(%SYS.ProcessQuery).GetOSUsername()cacheusr [/quote]
go to post Ben Spead · Feb 3, 2022 @Jeffrey Drumm - it is important to have this run from a process that is already running in the InterSystems IRIS instance (or something spun off from the SuperServer) so that it doesn't pick up your UNIX username if you enter via console. So being able to run an API like Tim's will work nicely as I can run it via the Output window from Studio:
go to post Ben Spead · Feb 3, 2022 Perfect!! Exactly what I was looking for - thank you @Sarmishta Velury (and @Jean Millette and @Timothy Leavitt )
go to post Ben Spead · Feb 3, 2022 Note - more details on this topic can be found here: https://community.intersystems.com/post/git-shared-development-environme...
go to post Ben Spead · Feb 3, 2022 NOTE - to see the presentation launching this at the 2021 Global Summit, see this article: https://community.intersystems.com/post/video-git-gitlab-shared-developm...
go to post Ben Spead · Feb 3, 2022 Thank you @Craig.Regester for the response. Looking up that file in the docs (https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?...) it tells me that "For security reasons, the parameters.isc file is accessible only by the root user." I am pretty sure there is a way to tell what it is currently running as without needing that level of access. But it is good to know about this in the cases where root access is an option
go to post Ben Spead · Feb 3, 2022 Is there a single development server which all developers connect to? If you are not able to have a fully isolated development environment for each developer then you will end up getting frustrated trying to use client-side source control. You might want to consider the new server-side Git source control hooks which were recently launched: https://community.intersystems.com/post/git-shared-development-environments This won't solve your issue of working while not on VPN, but it will allow multiple developers to work against the same instance without stepping on each others' toes.
go to post Ben Spead · Feb 3, 2022 I know this is an old thread, but we do have a solution available now for this scenario which will work with Studio, Atelier or VSCode. See https://community.intersystems.com/post/git-shared-development-environments
go to post Ben Spead · Jan 28, 2022 @Matthew Giesmann - thank you for this write-up ... I hope it helps someone else avoid some head scratching!
go to post Ben Spead · Jan 28, 2022 @Don Martin - It looks like there a typo: its "irishealth-ml-community", not "irishealth-community-ml" Try podman pull containers.intersystems.com/intersystems/irishealth-ml-community:2021.1.0.215.3 (credit to John Martin in ISC RelEng)
go to post Ben Spead · Jan 25, 2022 nice article, thank you for sharing. Small note - Download is misspelled in the first step of your directions
go to post Ben Spead · Jan 24, 2022 Please note that 2021.2 is also available via the InterSystems Evaluation Service: https://evaluation.InterSystems.com. If you are a supported customer you can request evaluation keys or get full/community edition kits/containers. Prospects can get Community Edition kits/containers (see https://community.intersystems.com/post/introducing-evaluation-service-c...).
