If you are beginning your journey with Senzing, please start with Senzing Quick Start guides.
You are in the Senzing Garage where projects are "tinkered" on. Although this GitHub repository may help you understand an approach to using Senzing, it's not considered to be "production ready" and is not considered to be part of the Senzing product. Heck, it may not even be appropriate for your application of Senzing!
A docker container that gives a web-based terminal.
Similar to ssh
, but over HTTP/S.
The senzing/xterm
container is a web application that creates the facade of a Xterm window.
Behind the scenes, keystrokes typed into the web-based Xterm window are sent via socket to the running docker container
to be executed within the container. The results of the command are sent via socket back to the web Xterm window.
Senzing commands such as G2Command.py
, G2Explorer.py
, etc. can be executed in Xterm.
To access files outside of the container, files should be place on volumes mounted to docker container.
:pencil2: Identify a port to view XTerm. Example:
export SENZING_XTERM_PORT=8254
Run Docker container. Example:
sudo docker run \
--rm \
--publish ${SENZING_XTERM_PORT}:5000 \
senzing/xterm
The web-based Senzing X-term can be used to run Senzing command-line programs.
If SENZING_XTERM_PORT
was set to 8254
,
Senzing X-term will be viewable at
localhost:8254.
In general, visit the web address having the following format:
http://${SENZING_XTERM_HOST}:${SENZING_XTERM_PORT}
Example:
export SENZING_XTERM_HOST=localhost
export SENZING_XTERM_PORT=8254
becomes http://localhost:8254
.
See additional tips for working with Senzing X-Term.
View license information for the software container in this Docker image. Note that this license does not permit further distribution.
This Docker image may also contain software from the Senzing GitHub community under the Apache License 2.0.
Further, as with all Docker images, this likely also contains other software which may be under other licenses (such as Bash, etc. from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.