go to post Dmitry Maslennikov · May 13, 2022 Is it for production use or for development? In production, you should separate the web in a separate container with own web server and cache settings. If it's in development, and your web folder is mounted outside of the container, it looks like just a caching on WebGateway. Change Serve Files to just Always, instead of default Always and Cached
go to post Dmitry Maslennikov · May 8, 2022 It does not look like OmniDB is in active development anymore. But I found that it uses Django, so, I can try to use my project with Django IRIS support there.
go to post Dmitry Maslennikov · May 8, 2022 It's better to look at something like Grafana. Here are a few articles about using it. Big article with many details and my article with direct connection to IRIS If you need some help with the development and configuration of such monitoring, I can help with it.
go to post Dmitry Maslennikov · May 2, 2022 Both still return 1 character for numbers up to 16 II would recommend this way, instead $Translate($Justify($Zhex(dec),2)," ", 0)
go to post Dmitry Maslennikov · Apr 11, 2022 It's the only reasonable way to go. It's a bad idea to store such data as %String I would suggest wrapping this field with Get and Set to make it compatible with the previous storage
go to post Dmitry Maslennikov · Apr 9, 2022 Yeah, you may find a few articles about some different ways how to do this, but mostly based on using Docker Gitlab CircleCI and Azure GitHub Actions and AWS EKS
go to post Dmitry Maslennikov · Apr 9, 2022 yes, for sure, it's possible, and there are many ways to implement this And possible to select one of the ways, from what you are already familiar with.
go to post Dmitry Maslennikov · Feb 28, 2022 Javascript setTimeout(function() { document.location = document.location }, 5 * 60 * 1000)
go to post Dmitry Maslennikov · Feb 25, 2022 So, host.docker.internal is 192.168.65.2 and it's the same network as in settings, but this IP is used to get access from the virtual docker's environment Could you try to use one of your real host's IP, which comes from Wi-Fi for instance my wifi gives me IP 192.168.1.170, and it works
go to post Dmitry Maslennikov · Feb 25, 2022 127.0.0.1 will not work, due to it's still different host, and in case of this sam bundle, it should point to sam's iris. And will not work it, because, it should be available for prometheus container, not just for IRIS container for sam. So, you have to use, it's name as a host iris And to access, some IRIS external to docker, you may use host.docker.internal hostname, or docker.for.mac.localhost with Docker on macOS So, the first line is points to SAM's IRIS, and second to an IRIS outside I think host.docker.internal was added in some recent versions of Docker, so, probably check the version of Docker
go to post Dmitry Maslennikov · Feb 25, 2022 This is how Durable %SYS works, when it's initialized, it copies everything to the durable folder, including your db in mgr directory. And you can prevent it, by creating this database, just somewhere else.
go to post Dmitry Maslennikov · Feb 25, 2022 Caché will not get support for M1, and so, I think no reasons to wait for an ODBC driver for M1 too
go to post Dmitry Maslennikov · Feb 25, 2022 And I have one more demo project, based on Realworld application, I found on GitHub What I did, is just forked some project, switched it to using IRIS, by configuring its settings, added requirements, wrapped it in the container with IRIS, and that's mostly it. Look at the repo https://github.com/caretdev/django-iris-realworld For this project, I've used a non-CE version of IRIS, so, you will need an iris.key, placed in home directory to start it
go to post Dmitry Maslennikov · Feb 25, 2022 It's not a big issue, to make it work. Just keep in mind that both containers, with SAM and monitored system, have to be in the same docker's network. If you run both images in with docker-compose, they by default will get the same network, so, in most cases, you may use IRIS service's name from docker-compose.yml as a hostname, and it will be able to connect to it internally inside that network. If you need access from dockerized SAM to a dockerized IRIS, both working in different networks, you have to publish ports for IRIS, so, it should be available from the host, but from the docker, your SAM has to know the host's address and host.docker.internal is a way, to give it to him. And port should be the same as published when docker container is running. When docker container is started with -p param, which says how to publish the port, possible to say, which IP to select, or select all for instance -p 0.0.0.0:52273:52273 docker ps, may help with understanding how the container is available 8d8977f9d5f8 intersystemsdc/iris-community:preview "/tini -- /iris-main…" 6 days ago Up 3 days (healthy) 0.0.0.0:1972->1972/tcp, 2188/tcp, 53773/tcp, 0.0.0.0:52773->52773/tcp, 54773/tcp iris if it shows something like 127.0.0.1:52773->52773, it will only be available as localhost or 127.0.0.1 and will not be accessible from another container and network, because of host.docker.internal will refer to another ip Could you explain, how you running all the parts?
