Some time ago GitHub, has announced the new feature, GitHub Codespaces. It gives an ability to run VSCode in the browser, with almost the same power as it would run locally on your machine, but also with a power of clouds, so, you are able to choose the machine type with up to 32 CPU cores and 64 GB of RAM.

Looks impressive, is not it? But how it could help us, to work with projects driven by InterSystems IRIS? Let's have a look, how to configure it for us.

NOTE: This content was originally presented at the InterSystems Global Summit in 2014, however related topics often come up on the Developer Community so I have decided to turn this into an article for easier reference and discussion. However, much of the content was pulled directly from the presentation slides so the article format resembles that of a PPT deck more than paragraphs.

Hi developers!

Let me share with you a minimal embedded python template, that I can recommend as a starting point for any general project with InterSystems IRIS that will use embedded python.

Features:

• Embedded Python ready;
• Examples of 3 ways of Embedded python development;
• VSCode development ready;
• Docker enabled;
• Online demo enabled;
• ZPM First development ready.

Let's discuss the features below!

Hey Community,

New video is already on InterSystems Developers YouTube:

⏯ Git & GitLab for Shared Development Environments

https://www.youtube.com/embed/elVQEU9MitE
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

For a solo developer developing web applications what will be the best technology to use IRIS or Studio with cache database and containers for deployment

Hi all, I have released the latest version of VSCode extension for ObjectScript already a month ago, and finally a time for the info about this new release.

So, what's new in the release:

What's new in this version

• added export setting "objectscript.export.addCategory" if enabled uses the previous behaviour, adds category folder to export folder, disabled by default
• added Server actions menu, by clicking on server info from status bar. Open Management portal, Class Reference and toggle connection.
• Class Suggestion in ##class, Extends, As, CompileAfter, DependsOn, PropertyClass
• $SYSTEM suggestion by Classes from %SYSTEM
• Import and compile folder or file by context menu in File Explorer
• Server Explorer, now possible to open any other namespace
• Macros suggestion

For details how it works now, look further.

The Atelier beta update channel:

https://atelier.artifactoryonline.com/atelier/updates/beta/1.1

offers the latest features and bug fixes. It now updates your installation of Atelier to build 1.1.291 for Mac, Windows, Red Hat and SUSE. Here’s an account of what’s recently been improved:

New Features:

One of the many benefits of using Atelier for your ObjectScript development is its integration with a wide range of source control systems. This integration enables you to use modern development workflows which increase collaboration while minimizing the risk inherent to volatile code bases.

Veteran ObjectScript developers can tell you about the workarounds that were needed before they could use source control systems with products like Caché and Ensemble. One of these was to treat the data store itself effectively as a code repository. And so shared development environments became essential for many of our customers to be productive and successful.

For code shops that rely on shared development environments, adopting Atelier might seem too complicated. This article aims to provide a practical example to guide your team towards success with Atelier.

You can find an overview of the problems and solutions in this article here, which is a good place to start. This article assumes that you are familiar with the concepts introduced there.

I want to be able to view generated items from visual studio code. In Studio there was an option in the open dialog:

Specifically, I added a namespace to my workspace for editing (Using InterSystems Server Manager) and I want to be able to access the generated items in this namespace.

I want to demonstrate using Git via Server-side Source Control hooks (to allow both Studio and Atelier to access a Shared Dev namespace), and I was planning to use the popular Caché Git hooks:

https://github.com/intersystems/cache-tort-git

Adding VSCode into your IRIS container

One of the easiest ways to setup repeatable development environments is to spin up containers for them. I find that when iterating quickly, it was very convenient to host a vscode instance within my development container. Thus, I have created a quick container script to add a browser-based vscode into an IRIS container. This should work for most 2021.1+ containers. My code repository can be found here

As most of you have heard already, InterSystems announced the deprecation of Studio with the release of IRIS 2023.2.

I understand this is a rather broad topic (and at times involves religious sentiments) yet I would like to look at it from the Caché perspective:

Thanks for all replies in advance. In monitoring our audit log we are getting the error below. We have 4 different servers running CACHE 2014.1.1 and this is happening on all 4 of them. I have not been able to find what process is trying to logon but it is happening every 30 minutes. We have no user processes that are running so this has to be a CACHE process. Does anyone have an Ideal what could be running to cause this? What kind of trace can I run to determine what process is running it?