You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be doable to use docker-java or similar to build a local container from either the official or community Domino Docker images and use that to do the actual execution, especially since the process already involved spawning a sub-process anyway.
It would make sense for this to allow specification of an ID file and other parts to use to do the actual building, and to otherwise build using a temporary-spawned name from a domino-config.json file.
The text was updated successfully, but these errors were encountered:
The initial commit adds support for auto-configured hclcom/domino:12.0.2 containers, which are useful for compilation and export. A few things remain to cover other capabilities:
Adding classpathJars to the ndext directory
Allowing specification of a custom base image
Allowing specification of a custom server ID
Potentially allowing specification of advanced server-setup properties: existing server, connection docs, etc.
It should be doable to use
docker-java
or similar to build a local container from either the official or community Domino Docker images and use that to do the actual execution, especially since the process already involved spawning a sub-process anyway.It would make sense for this to allow specification of an ID file and other parts to use to do the actual building, and to otherwise build using a temporary-spawned name from a domino-config.json file.
The text was updated successfully, but these errors were encountered: