Congratulations to everyone for a great 2021!!
- Log in to post comments
Congratulations to everyone for a great 2021!!
Glad to see this contest and what comes out of it!!
excellent article - thank you so much @Robert Cemper !!
Is there a single development server which all developers connect to? If you are not able to have a fully isolated development environment for each developer then you will end up getting frustrated trying to use client-side source control.
You might want to consider the new server-side Git source control hooks which were recently launched:
https://community.intersystems.com/post/git-shared-development-environm…
This won't solve your issue of working while not on VPN, but it will allow multiple developers to work against the same instance without stepping on each others' toes.
I know this is an old thread, but we do have a solution available now for this scenario which will work with Studio, Atelier or VSCode. See https://community.intersystems.com/post/git-shared-development-environm…
@Matthew Giesmann - thank you for this write-up ... I hope it helps someone else avoid some head scratching!
@Don Martin - It looks like there a typo:
its "irishealth-ml-community", not "irishealth-community-ml"
Try
podman pull containers.intersystems.com/intersystems/irishealth-ml-community:2021.1.0.215.3
(credit to John Martin in ISC RelEng)
nice article, thank you for sharing.
Small note - Download is misspelled in the first step of your directions
Great article. thank you!!
Please note that 2021.2 is also available via the InterSystems Evaluation Service: https://evaluation.InterSystems.com. If you are a supported customer you can request evaluation keys or get full/community edition kits/containers. Prospects can get Community Edition kits/containers (see https://community.intersystems.com/post/introducing-evaluation-service-…).
Thank you very much @Evgeny Shvarov !
well said @Timothy Leavitt!! This is *exactly* why I love ObjectScript so much as well :)
excellent article - thank you!!
Congratulations to the winners!!
@José Pereira , thank you for sharing!! Please note that you have a small typo in your title - pratical > practical (no worries, if I wrote a D.C. article in Spanish you would lose count of all of the typo's ;) ).
Quick note that the Announcement has been updated to include links to the specific course PDFs as well as links to the online version of those courses where one is available.
We are still looking for some more people from our larger implementation community to take part in this Beta Test - please sign up today if you haven't already done so! (and THANK YOU in advance :) )
nice job @Timothy Leavitt - definitely a Best Practice :)
@Yuri Marx - thank you for all of your contributions :)
Nice work everyone!!
Nice job everyone - congratulations and thank you for your contributions!!
Thank you @Adam Coppola !!
You should still be able to get into the instance while it has an expired key ... you just can't make multiple simultaneous connections to it. You can also grab the iris.dat files from the file system (which actually stores the globals) and then mount them to another instance. Or you can just upgrade that instance to a new version of the Community Edition (which is likely the easiest approach)
Rob ... this is incredibly rich - thank you for taking the time to write all of this up!!
Wow - that is so cool!! Thank you for sharing @Joel Solon :)
It should be safe to edit manually as long as you are not changing the piece numbers or changing the order around. Simply changing the property name within <Value>...</Value> of the storage definition should be fine if it is no longer used at all. In our case, we have had instances in the past where we needed to change a property name and rather than creating a new property and migrating the data it proved to be safe and much more efficient to change the property name in both the property definition and the storage definition (as well as all of the places in the source code which refer to it). The nice thing about this approach is that we've been able to simply do a Find/Replace in all of the source code and carefully review the diffs before submitting.
If others are aware of gotcha's when changing the storage definition Value, I would be interested in hearing them.
BRAVIO G.M. TEAM!!!
Great analogy @Vivian Lee!! Thank you for writing this up :)
as Vivian explained, you can delete the property definition and then change the name in the storage definition to make it clear that that slot should be ignored. This of course should be done while keeping versions of everything in source control so that the reason for the change is documented and discoverable in the future should someone need to understand why the property was removed.
Thanks for quick fix @Evgeny Shvarov!! Also, thanks for the details that some types are not supported, that is good to know. At this point I think I am good with letting it take it's best guess and then editing the class afterwards if needed. With SQL LOAD coming hopefully there will be less need to one-off utilities that do this but I am thankful that it was available for what I needed this week!!
Wow - this looks like it is going to be an incredibly helpful feature!! Thank you for pointing out the new docs on it :)