Supported tags and respective
STOMPCLT is a versatile tool to interact with messaging brokers speaking
STOMP and/or message queues (see Messaging::Message::Queue) on disk.
It receives messages (see Messaging::Message) from an incoming module,
optionally massaging them (i.e. filtering and/or modifying), and sends
them to an outgoing module. Depending on which modules are used, the tool
can perform different operations.
Documentation for this script is available at http://cern-mig.github.io/stompclt/
License and Copyright
Copyright (C) CERN 2012-2016
This program is free software; you can redistribute it and/or modify it
under the terms of either: the GNU General Public License as published
by the Free Software Foundation; or the Artistic License.
See http://dev.perl.org/licenses/ for more information.
STOMPCLT Image Documentation
The following configuration files and volumes need to be prepared in advance:
- /etc/stompclt with one or multiple stompclt configuration files (one configuration file per container is supported)
- outgoing/incoming directories referred in the configuration file are expected to be mounted as volumes
The basic operations on the container:
start-up $ docker run -d --name stompclt \ -v /var/spool/stompclt/outgoing:/var/spool/stompclt/outgoing \ -v /etc/stompclt:/etc/stompclt \ mbabik/stompclt:1.5.1 --conf /etc/stompclt/stompclt.cfg debug $ docker exec --name stompclt ps -ef $ docker logs -f stompclt $ docker exec stompclt /bin/bash upgrade to new image $ docker pull mbabik/stomplct:<new_tag> $ docker stop etf_ps $ docker rm etf_ps -> start-up
Supported Docker versions
This image is officially supported on Docker CE version 17.03.0.
Support is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
If you have any problems with or questions about this image, please contact us through a GitLab issue.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitLab issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.