go to post Dmitry Maslennikov · Sep 26, 2018 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.
go to post Dmitry Maslennikov · Sep 22, 2018 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.
go to post Dmitry Maslennikov · Sep 21, 2018 Recently I already mentioned project Cube for macOS, which can be used to easily get access to Management Portal and terminal
go to post Dmitry Maslennikov · Sep 18, 2018 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?
go to post Dmitry Maslennikov · Sep 18, 2018 Caché cube icon available only for Windows. But there is an external project Cube, but it was not developed so long.
go to post Dmitry Maslennikov · Sep 7, 2018 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.
go to post Dmitry Maslennikov · Sep 6, 2018 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.
go to post Dmitry Maslennikov · Sep 6, 2018 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.
go to post Dmitry Maslennikov · Aug 30, 2018 Interesting task, and actually it is possible to implement.
go to post Dmitry Maslennikov · Aug 30, 2018 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.
go to post Dmitry Maslennikov · Aug 30, 2018 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.
go to post Dmitry Maslennikov · Aug 29, 2018 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)
go to post Dmitry Maslennikov · Aug 23, 2018 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.
go to post Dmitry Maslennikov · Aug 16, 2018 You can specify /nodelete qualifier when you run your tests. Do ##class(%UnitTest.Manager).RunTest("testspec","/nodelete") Look at the documentation for other options.
go to post Dmitry Maslennikov · Jul 26, 2018 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?
go to post Dmitry Maslennikov · Jul 11, 2018 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?
