ontariosystems / iscenv

This utility allows the user to manage docker-based ISC product instances

ISCEnv

This utility allows the user to manage docker-based ISC product instances. These instances are meant to be used as development environments on a Linux host.

Usage

The command consists of a single command line utility iscenv. This utility is self-documenting. Please refer to its help for further documentation on each command.

Caveats

• Do not add a default namespace to the root user on the instance, this will break features that wrap csession as it can no longer use the -U switch

Known issues

• Orphaned plugins are occasionally left running after the primary process exits. This prevents upgrades. They can be killed by (after stopping all running iscenv containers) executing killall iscenv

Future changes

• Rework plugin system to use go plugins (simple example)

Rejected Features

• Make all commands return the instance name rather than the container ID We're using full logging now rather than specific items being printed to stdout
• Add Service wrappers for the containers which will restart them on reboot We want iscenv to remain thin, users should do this themselves
• Have prep update the deployment service Removing the deployment service from ISCEnv altogether
• Add a command that reads a simple configuration file to set up a specific environment
  Just use a simple bash script
• Make "prep" an external that does the ssh to the container, make another internal weird named prep that it uses
  The purpose of this was to allow prep to be called again on an existing instance. Instead just recreate the instance using start --rm.
• Add the ability to recognize when running in a repository and name the instance after the repository, use Gem to determine the version, use a .file to determine the port.
  This could be a secondary tool but does not belong as part of this tool. It ties us too many external systems and complicates this simple single purpose tool.

iscenv's Issues

Rework plugin system to use go plugins

Rework plugin system to use go plugins (simple example)

Add the ability to attach volumes

Currently you can specify volumes if you have iscenv _start set as the entrypoint and running via docker run. However, when managing a container with the iscenv command line volumes-from is the only volume management that is available. Support for --mount and probably --volume should be added.

Publish on InterSystems Open Exchange

Make an entry in Open Exchange apps gallery?

Change from linked containers to docker network

Currently additional containers are connected to the main container by container linking, a legacy feature. This should be replaced by having a docker network that the containers can share.

The csp lifecycle plugin should allow mounting of apache or ngnix configuration

The containers.intersystems.com/intersystems/webgateway or containers.intersystems.com/intersystems/webgateway-nginx images from https://containers.intersystems.com/ don't have any websites defined (such as apache VirtualHosts or nginx server). It would be nice to be able to provide a path to a website to use in the container that's started.

Something like:

iscenv start --csp-conf-dir /path/to/apache/config --version 2023.3 example

This maybe could be related the the volume mounting mentioned in #2