Now answering your question :) 

Name="src" means the folder related to the one where module.xml is situated on the development/testing or publishing machine.

In order to protect the IP you can use "Deployed packages" mode, see the documentation. Just include Deploy="true" in a resource element, and only compiled code will be installed. 

  <Resource Name="Sample.Demo.PKG" Deploy="true"/>

Load command locally still will import package with the source code, which is quite handy for development and testing.

Hi @Stephen Canzano !

Unit tests are not included into the package when you publish it into repository. So when you install the package on a target machine only "solution" classes will be installed, not unit-tests.

E.g. here is csvgen app. I you check the source code it contains "solution" classes in src folder here and unit-tests in /tests folder.

module XML for csvgen has resources, that will be packaged while published in the IPM registry:

<Resource Name="community.PKG"/>

and the unittests, that are being used only development phase and can be imported to the system via load command:

<UnitTest Name="/tests" Package="community.csvgen.UnitTests" Phase="test"/>

So when you install csvgen package, e.g.:

USER>zpm "install csvgen" 

you'll see only RESOURCES classes installed.

Thank you, @Steve Pisani !

This is a fantastic discussion. Is there any service other than @Lorenzo Scalese's that can provide host IP and port for a docker iris? e.g. to be able to use it during development? 

That works, Robert, thank you! Not for docker use unfortunately

Nice! Thank you @Brett Saviano! 

And it works for host versions nicely! But of course if it is a docker image there could be a ports mapping. e.g. if I start iris with the following command:

docker run --rm --name iris-demo -d -p 9091:1972 -p 9092:52773   intersystemsdc/irishealth-community:preview

and open terminal with:

docker exec -it iris-demo iris session iris

then the command gives us:

USER>Do ##class(%Studio.General).GetWebServerPort(,,,.url) Write url,"csp/sys/UtilHome.csp" Kill url

http://172.17.0.2:52773/csp/sys/UtilHome.csp

and the working one is:

http://localhost:19092/csp/sys/UtilHome.csp

Maybe it is not possible at all for docker. 

Unless we setup a special global intentionally during the docker image build.

BTW, @Sylvain Guilbaud , @Robert Cemper , @Alexander Pettitt  - do you think if it is possible to have a shortcut command that will return the URL for a management portal in terminal? with a proper port and CSP app?
 

Thanks @Robert Cemper !

Thank you, @Sylvain Guilbaud !