Thanks, for such a good project. Hope to see open source repository with it.
- Log in to post comments
Thanks, for such a good project. Hope to see open source repository with it.
Thanks, I had not noticed Problem View before. But now I see that problem in some file, which was found by Atelier in a project folder. And in my case, error was File is too large to parse properly for file jqeury.min.js.
Interesting, it is a very good task for Docker.
It is a very different question, please create as a separate one.
w #,*27,"[32m" s $lb(tw,th,twi,c,tp,l)=$lb(2,4,8,40,4,24) while (l-th>tp) { f st=0:1:th-1 { s y=tp+st,x=c-(tw/2),w=tw-1 s:w ts(y)=$lb(x,w) w *27,"[",y,";",c-(tw/2),"H/",*27,"[",y,";",c+(tw/2),"H\" s tw=twi/th*2+tw } s tp=tp+th,tw=tw-twi } w !,*27,"[0m","Press any key to exit" f { w *27,"[",y,";",x+1,"H",$j("",w) f i=1:1:y\4 { w *27,"[",$r(10)+30,"m",*27,"[",y,";",$r(w)+x+1,"Ho",*27,"[1;1H"} s y=$o(ts(y),-1,d),$lb(x,w)=d i w<5 {s y=$o(ts(""),-1) h 0.3} r q:0 q:$t } w *27,"[0m"
Tani, please change all terminal samples and samples of code from pictures to plain formatted text.
I would recommend to use a bit modern way
set rs=##class(%Routine).RoutineListFunc("ABC*.int")
while rs.%Next() {
write !,rs.Name
}
Well, there are some different reasons to do it:
Plase add some more details, what do you mean by slowly?
Do you work remotely? Is it still slowly if connect locally on the server?
Thanks, and thanks for your articles hope to see next article soon.
Sure, leading zero, so, fixed code.
set hashHex="" for i=1:1:$l(hash) set hashHex=hashHex_$translate($justify($zhex($a(hash,i)),2)," ","0")Yes, and cloud of tags, does not show that hierarchy. And when I search needed tag by typing while create new post, too.
So, hierarchy here looks useless.
You can reset all changes which you did, when you start newly created container from an image. Use docker run with a flag --rm to remove container after exit.
Even more interesting that, GitLab has their own docker registry. And you can even build your own image for ci with ci.
We build Ensemble container. You can look at archive of my project ensemble.zip . Simple image with Ensemble, without Samples and Docbook databases with minimal security.
In current stage, we do not have any Caché code, yet. But I don't see any troubles here. You may use base Ensemble image, and run it on GitLab environment, or on your own server, via gitlab-runner and preinstalled Ensemble. With GitLab-CI, possible lots of different ways.
Please add more details, how did you try to do it, and $zversion of your instance.
this version number is not enough, please show output from this command
write $zv
Looks like, your installation in 8-bit mode instead of Unicode. In that case such behavior possible. That's why we are asking for full version name from $zv,
As the last argument, you should use routine or classmethod, not command.
csession CACHE -U"%SYS" "##class(%SYS.System).InstanceGUID()"
Please put some example of your code here, and how exactly you call your REST.
Yes, it is possible
Why do you think it should be in this part of the documentation. It usual procedure. Almost everything possible to do programmatically, so, you can write a script for it. And there are lots of ways ho to do it. As for me, I think the bast way is to use Installer manifest.
Because, your UrlMap define only GET method, If you need more, you should add it to the same or any other methods.
And with CRUD, you should not put delete/insert inside URL, just use different HTTP methods with the same URL.
I've been working with Caché now a bit less than before. But anyway I see that Atelier very slow, I'm typing much faster, then it can show what I wrote. And still exists some highlighting errors, which I've already described earlier.
As it is opened project, you can fill an issue directly on that repository. So, developer may get notification about it quite quickly to respond.
Thanks, sure, fixed
Stay tuned, I'm going to write next about it. In this article, we did a basic image. Wich will be as a source FROM for next images with some our application.
I think in this case better to use property ReplyTo, which will be used in mail clients as an address for response.
Alexey, yes, it is very easy to build a little application just in one container. I don't see any problem, to use any supported technologies as well. Even also possible some load balancing from docker, which also good for microservices. I'm going to show some example with application in the next article soon.
Hi, I would not recommend thinking seriously about Caché in windows server core container, I think it is too early, yet.
Stay tuned, I'm going to show how to do it the next part.