ODKRunner 0.3.0

Changes since version 0.2.1:

• The runner can be configured through ODK_ environment variables as an alternative to a run.sh.conf file (not recommended, but for compatibility with the ODK-generated run.sh script).
• The max memory setting for Java applications can now be explicitly be set on the command line through the -m, --java-mem option.
  • That option takes precedence over any -Xmx option passed through ODK_JAVA_OPTS.
  • The --java-mem value should be of the form Xm, Xg, or X%, to set the maximal amount of memory to X megabytes, X gigabytes, or X percent of the available memory, respectively.
  • The default behaviour, when that option is not used, is still to use 90% of the total memory available to the backend.
• If the environment contains typical variables used for proxy configuration (http_proxy, https_proxy, no_proxy, or their uppercase equivalents), the proxy settings are automatically passed to the container.