Silent install uses exactly the same manifest file, as for interactive. And it will install all components. But you can choose which one you really need with ISC_PACKAGE_CLIENT_COMPONENTS parameter and when this parameter empty will be installed all components.
Why do you need so? By default with silent install, will be installed all components. But if you need to switch off some packages, you can configure really custom installation. More details in the documentation.
InterSystems has licenses for Linux various systems, so, they can offer license for it, and they have license type especially for docker version based on ubuntu.
I'm don't see any issues in performance, and mostly because I don't have so much big projects, yet, and don't use it in production. Current cases are only CI/CD.
Well, how I would dive into this issue.
Of course, this way not so easy to realize, and depends on how you deploy code in production. Or maybe it even possible to measure in the testing environment.
if you working on Linux, you can try to use device-mapper as storage-driver, which is also supported by InterSystems.
This behaviour expected if you use default Docker configuration, look at mention about aufs above in comments.
But, you should use docker version 18.06, because in newest version already deleted support for AUFS, and InterSystems does not work on overlay driver wchich is used by default in Docker.
when your container run, and you can find it in running state, you can use command
docker ps -a
which will show all existing containers in any state.
and then you can look at the logs of particular container
docker logs `hash shown after run command or assigined name visible in docker ps -a`
It happens because you still have $ensemble, replace all occurrences, and everything will be okay
looks like you did some changes in your Dockerfile comparing to my example, and you did mistake there. Can you share your Dockerfile, so I could check it?
In my example I have line
ADD $cache-lnxrhx64.tar.gz .
where $cache is variable defined few lines above. And when build will run, it will be replaced with value. But in your case, I see $ensemble, and sure that you don't have such variable, and this follows to the error.
Check it now, should be ok
I was not sure if it works, but looks like it does not work anymore. You can try to fill issue, and maybe author will repair it.
I already did it by myself, through the form.
I have not touched Trak before, but I'm sure they don't use plain CSP pages and use at least CSP classes. Why do you need CSP files?
I have configured automatic deployment of the application to Kubernetes with Helm from GitLab as a part of CI/CD process.
I would not say that I had some specific issues, just well configured Kubernetes cluster with the right storage driver. Any InterSystems products supports devicemapper and aufs right now, yet. So, of course, better to have devicemapper available server, and use this possibility. AUFS already deprecated by Docker and will disappear in the next major release.
Sorry, it was my mistake, just missed that I wanted to hide websocket by rest, and did it not in good way. Issue was in my CacheBlocksExplorer project. Fixed it with ServerSideRedirect. So, now I can use only one CSP Application in public for REST and WebSocket.
I used Gitlab, to build and test application itself, build docker images and deploy it to kubernetes with helm. Used simple integration with Slack from gitlab, so, I have notifications about the status of any latest build.
Yes, I think I can do it.
Interesting task, and actually it is possible to implement.
I wanted to finish stable release, with support for new versions Caché and IRIS, and also release docker image to use it very easy. But unfortunately, I have not found time for it, yet.
Large databases should not be a big issue. Should work, it will show data asynchronously, so, how depends how fast disc it should show data anyway. And it should work as fast as the Integrity, or so.
Do not forget that $lb is just a list, concatenated list of single $lb, and $lb is a string in binary format.. So, just $replace, will work
USER>set list = $lb("stri,ng", $c(0), 2)
USER>set list = $replace(list, $lb($c(0)), $lb())
USER>zw list
list=$lb("stri,ng",,2)I made such an example years ago, you can look at GitHub. This example maybe not so correct by this time, but can be useful. When you have to run only ECP clients, it becomes a bit easier. You should not care about volumes, in most cases, all the data stored in ECP-client is temporal. So, you mostly should care only about buffers. In my example, you can find how to configure instance during docker build to work as ECP-client.
You can specify /nodelete qualifier when you run your tests.
Do ##class(%UnitTest.Manager).RunTest("testspec","/nodelete")
Look at the documentation for other options.
You can find detailed information in the documentation
Luca thanks for the response. Can you also say something about GKE, I did not find how to change storage driver, IRIS does not work there?
Well, now a few questions.
Does it mean that any new requested features will be declined to implement?
Any possibility to implement new features by own?
How about the future of Atelier API?
If InterSystems not going to extend Atelier anymore, maybe it's time to open sources Atelier or at least Atelier API.
Currently, it sounds like Atelier will get the same future as Studio, it means no future. Or am I wrong?
In addition to other answers, if want to operate with bits, you can use functions:
If you are going to work with H.264, I would not recommend to try to implement it in COS, it will not be fast enough. I'm not very know with this technology but I'm sure I know, it is too complicated and encoding should work in GPU. But it is impossible with Caché. I don't know why exactly do you need it, but I would recommend you to look at external tool ffmpeg, which is very useful and leader on work with video. And I think you can connect ffmpeg.dll, to work from Caché with $zf functions.
Well, there is mostly only one reason, why you can't mount your database and this issue mostly happens when anybody tries to migrate between different versions on different machines. And it is different localization settings. Like, your database uses some national global collation, and you try to copy it to the instance with different settings, where this collation does not supported. You should find mention about wrong collation in cconsole.log. So, then, you should set the same NLS, as in the first system and try to mount again.
Another possible reason is different blocksize in the Database. By default Caché uses 8KB blocks, but it is possible to have different block size, and instance should be configured for this particular blocksize, as well. cconsole.log should also contain error in this case.
Some other issues, which you can face, but they do not prevent database to be mounted.