A great teaser for the course, thanks for sharing, @Yuri Marx!
- Log in to post comments
A great teaser for the course, thanks for sharing, @Yuri Marx!
If the idea is to deploy the solution somewhere and make the web app created automatically I'd suggest using the ZPM.
ZPM can generate the necessary elements of the working web-app in your machine and put it in the module.xml description.
So the ZPM module will deploy the code and will create a web-app (or apps) on the target machine with proper settings - actually with exactly the settings that work on your development machine.
Here are the article and the video.
HTH
Thank you for contributing ideas! We submitted all of them to this Github repository and here is the kanban for 2021.
Welcome to implement the ideas and submit them to the InterSystems Grand Prix contest.
The part on Embedded Python is updated:
here is the template that could be taken as a foundation to build an Embedded Python solution with IRIS.
here is an article that describes Embedded Python usage and packaging with ZPM for deployment.
Thanks, Jose!
Yes, indeed ZPM option of delivering files to a target IRIS installation looks elegant and robust. Maybe it could be used not only for Embedded python but e.g. for jar-files delivery and data. @Yuri Marx, what do you think?
Thanks, Robert!
Thank you, Jeff!
Hi Sorin!
It's definitely possible to have a development server and deploy code to a production server.
Caché code could be maintained with Git of course.
For automation they are very welcome to use Github Actions, Circle CI, etc.
There is a question how to import codebase to a production server or any other deployment server - the basic approaches are:
Import using the repo folder and Installer.cls
Use InterSystems Docker images - this is a more IRIS way then Caché.
Hi @yeung elijah! Have you tried WebTerminal ? It can substitute IRIS Terminal for some cases.
Andre, could you please elaborate on this? There is ODBC/JDBC option. Terminal. Call-in. What else are you looking for?
Perhaps you are looking for the way to filter JSON?
do you want to try JSON Filter app by @Lorenzo Scalese ?
Calling @Luca Ravazzolo
Calling @Dmitry Maslennikov @Raj Singh and @John Murray
We are having a lot of requests that voting is not available!
Actually to vote for the contest you need:
1. Sign in to Open Exchange - DC credentials will work.
2. Make any valid contribution to DC - answer or ask questions, write an article, comment on any post.
Thanks, Botai Zhang!
Hi Yeung!
Do you want to try VSCode instead of Studio? It has ObjectScript plugin and dark mode )
this is fixed too
Hi participants!
In order to simplify the assessment for bonuses could you please include in the readme the links where your app uses a certain model type?
E.g.:
You also can consider the web-terminal by @Nikita Savchenko, which could be installed also via ZPM as:
USER>zpm "Install webterminal"
It doesn't support host in/out operations (for obvious reasons) but has code completion for methods and commands and a nice SQL shell. And it's a web app
Thought that with this module by @Robert Cemper and sql-rest-api one can export to JSON any global with SQL query.
e.g. like that:
SELECT * FROM rcc_G.scan where rcc_G.Scan('^ERRORS',37)=1 and id['Jour'Thanks, @Nigel Salm!
There is also another app from @Nikita Savchenko - Classes Visual Editor
Hope you’ll find it useful.
Hi Mike! It looks like that your docker space is over.
Call
docker system prune -f
and see if this fixes the problem.
Caution! This will delete unused containers on your laptop. make sure you don't have sensitive data or uncommitted code in it. Usually you don't
you said that server-side dev is the only option IRIS provides,
I meant IRIS, or Caché, or Ensemble - when developers really store and even edit code on the server.
Now that I've saved that file and it's on the server, to continue making changes I should open up the server-side file and continue editing from there? Or I can continue working on the local and it will overwrite the server side?
you can continue editing it locally sending it to the server for compilation/testing every time.
I think I'm seeing your point about commits then. I edit it locally, it's sent to the server, the server sends it to the repo, and locally I should pull down the repo before continuing any changes. Is that the idea?
The idea with starting from a local folder with files, which is connected with source control. So any changes to the files are automatically being tracked by the source control you use (git, svn, mercurial, whatever). You use the server only to compile/test things - no connection to source control needed on a server-side.
This is how things happen in almost any programming stack.
@Raj Singh - could we make a webinar for VSCode and approaches to code, connect, etc?
Looks like that people could benefit from such a webinar
Reading the documentation, I'm also confused if local development is even desirable? In my case I have IRIS community running docker and I have Cache 2018 running on my local machine (can't get IRIS locally as it's a work computer and locked down). In this case I probably just want to develop all my code on the server?
It's up to you, of course. Developing the code "sitting inside" the server it's sort of the option only IRIS provides.
If you think what's going on when you develop "on the server" is when you change the class you change it in some global on the server and when you compile it you send the global to the compiler. And when you good you try "not-to-forget" to export code into a file and commit/push to the repository.
I prefer to edit files from the first step and send it to the server for compilation/testing and then commit/push the file - I'll never forget it cause VSCode helps me to manage it nicely with changes and things like that.
And it's not a big deal where do I send it to compile/test - whether it is local IRIS in docker or host or any remote development server.