Conversation
|
This may be useful. Would be nice if we had a README that explains how to make use of this. |
|
I don't fully understand README necessity. Docker's READMEs usually contain:
This is a very simple and standard Docker image. The commands that I used are: docker build -t jimtcl . # build Docker image
docker run -it jimtcl # 100% equivalent to run `jimsh` in an interactive shellThese cover both point 1 and 2 and are trivial for whose know a little bit Docker. Poit 1 could be a little bit improved explaining Dockerfile's ARGs, while point 2 could be a little bit improved with some examples. For instance:
However both examples solves quite standard Docker usage issues, which are already well covered by official docker run docs. |
|
Perhaps what I'm getting at it is how is it useful? Is there some use case of jimsh in a docker image that is interesting? (as it is primarily designed to be an embedded language where it is linked into some larger application). |
|
Personally I use JimTcl inside OpenOCD, but scripts development is easier without involving it. Developing inside a running JimTcl Docker container is the solution I adopted to exclude OpenOCD from the equation. |
This PR aims to start (automatized) distribution of JimTcl through Docker.
I'm submitting a working Dockerfile, but probably this PR should be followed by Travis changes to build the Docker image and push it to the hub.