go to post Ben Spead · Dec 19, 2023 Great video covering the material, and awesome job by @Timothy Leavitt and team on the git-source-control package from OEX which makes this workflow possible. More details on the tool can be found here: https://community.intersystems.com/post/git-shared-development-environments
go to post Ben Spead · Dec 19, 2023 Thanks for the recap - it's great to see everything accomplished this year :) Thank you to everyone to added to our Community this year!!
go to post Ben Spead · Dec 19, 2023 A great resource for the Community - thank you for taking the time to write this!
go to post Ben Spead · Dec 6, 2023 Well done @Anastasia Dyubaylo - I love how the content is grouped for easy exploration. Keep up the great work everyone :)
go to post Ben Spead · Nov 30, 2023 I have just learned that there are issues with "eu-central-1" and they are looking to remove it. Could you please try another deployment using "us-east-1" and see if that fixes it?
go to post Ben Spead · Nov 22, 2023 @Mathew Rimmington - this is an open source package which is written and maintained by InterSystems employees for the good of the Community, but doesn't have official support in the same way that customers have official support for InterSystems IRIS or HealthShare. This package is very much still strongly recommended for use and new sites are coming on board all the time. We continue to invest in it and see it as a valuable tool for developers using a shared-dev model on InterSystems products. In terms of the issue you are seeing, what InterSystems product are you using, and what specific version? We will definitely help you work through the issues as much as we can. CC: @Timothy Leavitt , @Pravin Barton
go to post Ben Spead · Nov 21, 2023 I strongly recommend that you reach out to Support with these questions
go to post Ben Spead · Nov 20, 2023 I strongly suggest you contact InterSystems Support to ask about this.
go to post Ben Spead · Nov 14, 2023 thanks for taking the time to post your solution to others can benefit!!
go to post Ben Spead · Nov 14, 2023 my understanding is that there will be no changes made to those APIs, nor plans to deprecate them. That is what Bob was referring to when he said most orgs use their own monitoring solutions to consume the IRIS data (via those APIs) ... so the APIs will stay, but SAM as an out of the box consumer of the metrics will be deprecated
go to post Ben Spead · Nov 14, 2023 this is only the SAM container. the APIs it consumes will stay and there are no plans to deprecated those.
go to post Ben Spead · Nov 14, 2023 Colin ... I hope you're successful in that effort!! happy kicking ;)
go to post Ben Spead · Nov 13, 2023 @Colin Brough - this was recently discussed on a thread internal to InterSystems, and I credit @Eduard Lebedyuk for the following options, which were suggested within the context of Enabled/Disabled Business Hosts on different environments using the same Production (some don't apply to your question about logging and testing, but I include them all for completeness): 1. Track a separate production class for each environment.2. Use SDS to effectively disable Business Hosts (for example, by setting the Port property to an empty string).3. Create a custom adapter/business host that has SDS configurable setting "RealEnable", which would be checked in OnInit or OnProcess input.4. Use Interoperability Schedules, with Business Host always off/on. I think (1) and (3) would be most likely to work for you here. Also, it's not going to help you in the immediate term, but be aware that TestingEnabled (along with some other fields) is supported for SDS starting in InterSystems IRIS 2023.3 (I am very excited about that!!)
