The way when used one server and shared git user, not recommended. It actually makes not so much sense when every developer will save his changes like one.
And instead of Studio, I would recommend now using VSCode-ObjectScript, it already has git support from out of the box, and each developer will work with git separately, so, history will be more clear.
Max, it looks like just a typo in extension, fixing.
Hi David, could you check it with the latest beta version?
Hi Emmanuel,
This particular extension is for Visual Studio Code only, at the moment. Different IDEs I hope will come in the future. And possible for Visual Studio as well.
VSCode supports Cyrillic, so, don't see any possible issues with Hebrew.
Visual Studio Code and Visual Studio are two completely different projects. There is only one thing between them, both developed by Microsoft. Don't be confused by similar names.
So, you should not be worried to use VSCode and Visual Studio on the same machine side by side.
There two open-source projects
minimal version is 8
I suppose it should work with any version.
Yes, this webinar was recorded, and it will be published on youtube very soon, stay tuned.
Thank you guys for coming to our first webinar! Wow! I did not expect that there will be more than 80 participants! Thank you for your interest and support.
We will make more overview webinars further on. But if you want to dive deeper you can sign up for our online course!
The first 3 subscribers will get 50% off the price!!
Fill free to post any issues with VSCode-ObjectScript you faced here
Thank you Raj for high evaluation of my work! I am sure with the community support we will make a perfect solution for coding on ObjectScript.
Guys, in case you need any support or want to learn more about the solution, do not hesitate to contact me here or on the website caretdev.com
Hi Muni,
Thanks for the report, it looks like some bug, we'll check it.
For future best to report such things as an issues in the repo.
Thanks a lot, and congratulations to other winners as well.
You can install it with zpm
zpm "install blocksexplorer"
And it will be available on your server by URL, like this
It's a when you in one command get everything you need. The problem is, that it uses external tool imagemagick to convert resulying image in bmp format to png. That's why it's not as simple as may sound.
Another reason is do not anything to a working system. To gather information enough readonly access to the database.
I already mentioned, how to do it for a whole database. At the moment no way to specify just a global. Fill an issue ))
Possible reasons
Just my thoughts
Any IRIS edition includes formerly known as Ensemble feature, which is now is Interoperability (and one of the letters in IRIS).
You may get this error if you work in the namespace where Ensemble was activated. By default for USER was not activated.
When you create a new namespace Ensemble checkbox checked by default and, but you can uncheck it.
to enable namespace manually, do this command
do ##class(%EnsembleMgr).EnableNamespace("YOUR-NAMESPACE")%SYS>w $listvalid($lb("test"))
1
%SYS>w $listvalid("test")
0
%SYS>w $listvalid("")
1$listbuild is not an object, so, it's not a check as an instance of, it is only possible that variable is valid as $listbuild
$listbuild as just a string with a special format, so, that's why this will also return true
%SYS>w $listvalid($char(1)) 1 %SYS>write $lb()=$c(1) 1
because
%SYS>zzdump $lb() 0000: 01 .
Just a few days left to send your app for the contest, I'm already in. ))
So, to get own docker-running Cache, is quite easy.
You just need docker desktop installed on your mac. Then when it installed, and running. You'll be able to run it from the terminal by command.
docker run -d --name cache \ -p 1973:1972 \ -p 57773:57772 \ -v $HOME/cache.key:/usr/cachesys/mgr/cache.key \ daimor/intersystems-cache:2018.1
It supposed that you have valid cache.key in your home directory. And that your ports 1973 and 57773 is free to use. If you would like to change the port just change 1973 and 57773 with any you'd like to use.
This command will download the image (daimor/intersystems-cache:2018.1) from the public repository, and run it in the background.
You can control the running container by commands, wherein all subsequent commands cache is the name of the container from the docker run command.
To see cconsole.log of the container.
docker logs cacheTo look at the status of the container
docker ps cacheStop running container
docker stop cacheThis is just an empty instance, to look at how it works. In the real case scenario, some more work should be done.
Docker images for Cache or for Ensemble are provided by me, and it is available for different versions.
Nowadays is best to migrate to IRIS, and use official images provided by InterSystems itself.
And the next step for you would be to use an editor that can be run on macOS, instead of Studio which working only on Windows.
And you can use VSCode editor with an extension VSCode-ObjectScript, developed by me.
I would recommend reading here articles tagged by Docker. There much more information about how to best use it.
As well as about using VSCode.
You can contact me directly, if you need any help with establishing development process, with such modern tools as Docker and VSCode. or migrating to IRIS.
I suppose you going to use it like for local development, not for production, so, I would recommend just use docker images instead. I'm using macOS and have not installed Cache/IRIS locally already for some years.
You did not provide the version you try to install and no cconsole.log. If you add this here, so it may help.
Yes, for sure, you can install any packages locally
ZPM> load /path/to/package -v
it can be as a folder, or as file tgz, which you can get with command
ZPM> package-name package -v
-v is optional, to get more logs for debugging
there are some possible issues to have docker related files in a dedicated folder.
When you would like to start an environment with docker-compose, you can do it with a command like this.
docker-compose up -d
but it will work only if the docker-compose.yml file name has not changed and it lays right in the current folder.
if you change its location or name, you will have to specify the new place
docker-compose -f ./docker/docker-compose.yml up -d
became not so simple, right?
Ok, next about Dockerfile.
when you build docker image, you have to specify context. So, the command below, just uses file Dockerfile in the current folder, and uses current folder as a context for build.
docker build .
To build docker image with Dockerfile placed somewhere else, you should specify it, suppose you still would like to have current folder as context.
docker build -f ./docker/Dockerfile .
any other files in the root, such as Installer.cls, irissession.sh or any other files which should be used during docker build have to be available from specified context folder. And you can't specify more than one context. So, any of those files should have some parent folder at least, and why not the root of a project.
with docker-compose.yml, we forget about docker build command, but we still have to care about docker-compose
The first iris after exec is the service name from docker-compose.yml, then goes command which has to be executed.
iris command is a replacement for ccontrol from Cache/Ensemble
session - subcommand for iris tool
And the latest iris as the instance name inside for IRIS inside the container
Sounds good. How about to run it on Raspberry PI, is it already a time, to order of some (even now, when it has been recently updated and got a lower price)?
It's great news, but when it will be available for preview.