Yeah, working with Environment variables is quite tricky, it may not be in a place where you would expect it. I would not recommend it for %Installer, you should focus on Variables feature there, and pass variable to setup method when you call it.
Hmm, why do you need to do it with .bash_profile? Why not just set it as a shell, instead of bash
And about passwords, the best and only right way in your case is to enable OS-Authentication. In this case users will go inside without a password prompt.
Just install a newer version over that old one, and everything will be ok. In some cases, it is possible that some changes in code would be needed. And you may look at the documentation for some information about the release
Most of the CI/CD processes are now based on Container's way. And do it without Docker makes this process much more complex. And It's not quite clear what do you want to achieve.
And in any way, this task is quite complex, and very much depends on what kind of application you have, how you build it right now, in some cases major OS, and even when some other languages and technologies are used for application. You may contact me directly, I can help with this, I have experience and knowledge on this.
docker exec -it iris iris session iris
Node: fa3f20fc42dc, Instance: IRIS
USER>w $zv
IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2021.2 (Build 617U) Thu Dec 9 2021 15:00:18 UTC
USER>:c
USER>:h
1: :h
USER>:a
USER>:sql
SQL Command Line Shell
----------------------------------------------------
The command prefix is currently set to: <<nothing>>.
Enter <command>, 'q' to quit, '?' for help.
[SQL]USER>> << entering multiline statement mode, 'GO' to execute >>
1>>q
[SQL]USER>>q
USER>:t
SQL Command Line Shell
----------------------------------------------------
The command prefix is currently set to: <<nothing>>.
Enter <command>, 'q' to quit, '?' for help.
dialect = MSSQL
[SQL]USER>>even :t for TSQL dialect
Nope, aliases not persisted, but :sql, :s works as SQL Shell without aliasing it
It looks like, it already persists somehow. I'm using docker, after halt command, I've entered the same container back with session, looked at :h and is history there, as well as aliases.
There are no reasons to have it Studio, instead I would recommend to have a look at VSCode, where is good support for JavaScript and for ObjectScript
set hr=##class(%Net.HttpRequest).%New()
set hr.Server = "server.com"
set hr.Location = "method"
do hr.InsertParam("name","value")
do hr.InsertParam("name2","value2")
do hr.Post("",1)And the result
USER>do ^test POST /method?name=value&name2=value2 HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; InterSystems IRIS;) Host: server.com Accept-Encoding: gzip Content-Length: 0
Internally it should support listbuilds, but not sure if it exposes this ability to public
And here it is, containers.intersystems.com gone
$ docker pull containers.intersystems.com/intersystems/irishealth-community:2021.2.0.617.0 Error response from daemon: Get "https://containers.intersystems.com/v2/": Service Unavailable
Could you push those images to the docker hub, as usual before? It's more stable.
Look at this project
Yeah, of course, you can change any class, if it's not a system and not deployed class stored in a read-only database
looks like you already know how to generate classes, so, to edit some method, you have to open a particular method by its id, which can be constructed from the class name and the method name.
USER>set method = ##class(%Dictionary.MethodDefinition).%OpenId("%Library.File||Exists")
USER>write method.Implementation.Size
56Well, Axure, is just a prototyping tool. And it does not have anything that would help to create something production-ready, with any kind of backend at all. It would be probably ok for designers to create some prototype of the application, or probably make something working, but only if no database is needed at all, such as a landing page.
So, I don't think that this tool could be considered in this role
Just as another option, I've recently published a project. Running in NodeJS, and connects to IRIS. It does not use an official driver and can be installed with npm (no readme, yet). Supports only SQL queries at the moment. You can look at this code, for example of usage. Just installing this package inside a Debian-based docker image with NodeJS, will be enough.
The most important thing you have to understand first, that when you use containers-way for running your application (and Docker here is just one of the ways, to run containers). You have to remember, that container should be as simple as possible, and do just only one thing. So, it means, that your NodeJS application, should run in a separate container, even if it connects to IRIS, it still has to be run separately and connected to IRIS over TCP.
So, you can use any official Debian-based NodeJS image, put InterSystems NodeJS driver in it, as well as your application, and run it. And your IRIS will run in a separate container, no matter which version.
It's a very interesting question. I think you mean something like some low-code platform.
I have not any of such and don't know about it. But suppose, such tools should work with a backend over REST.
If so, I see no reason, that it would not work with IRIS.
If you have some such tools in mind, could you share them, so, I would look, and check how easy it would be to connect to IRIS?
Ahh, did not notice you using x86_64 version, you need arm64 version, and it will be another image
store/intersystems/iris-community-arm64:2021.1.0.215.3
Just, to see if it’s not the durable %SYS issue, I would try to run it without durable. And you don’t need —init flag any more
The version 2021.1.0.215.0 of Community Edition contains an expired license. You’d need to use 2021.1.0.215.3 instead
It would not be safe to clean just everything there, on the fly. Alive processes may have expected some data in there.
The best way to solve it, to keep it cleaned well. You should try to figure out which globals have a bigger size. And if it's are part of your app, you may try to figure out which one could be cleaned safely and at what time.
Should work with Docker. And I would recommend this way
Windows 32bit, is not it? Only 64 bit is supported.
Actually, this way may also work in VSCode as well. It does support Attach to a process.
Unfortunately, there is no simple way of any debug for any web requests. And it does not really matter in docker or not.
What exactly, do you want to debug?
InterSystems Language Server extension
.png)
.png)