Docker image of xbus.broker
This image has been "applified" and behaves just like a binary application with several options.
docker run --rm xcgd/xbus.broker and see what happens :)
Don't hesitate to refer to the BitBucket project page for contributing, discussing and reporting issues.
This README is updated with regards to your questions. Thank you for your help!
This docker builds with a tested version of Xbus AND related dependencies. We do not intend to follow the mercurial repo because this is a production-ready docker image.
This is important to do in this way (as opposed to a nightly build) because we want to ensure reliability and keep control of external dependencies.
Current revision from https://pypi.python.org/pypi/xbus.broker:
You'll need the xcgd/postgresql Docker image or any other PostgreSQL image of your choice that you link with Xbus under the name
$ docker run --name="pg94" xcgd/postgresql
Note: read the instructions on how to use this image with data persistance. You also may use a distant server and change the configuration file accordingly.
redis (official build)
$ docker run --name redis -d redis:3.0.0
$ docker run -p 1984:1984 -p 4891:4891 --rm --name="xcgd.xbus.broker" --link pg94:db --link redis:redis xcgd/xbus.broker setup
$ docker run -p 1984:1984 -p 4891:4891 --rm --name="xcgd.xbus.broker" --link pg94:db --link redis:redis xcgd/xbus.broker start
You'll note that we did not open ports to the outside world on the PostgreSQL container. This is for security reasons, NEVER RUN your PostgreSQL container with ports open to the outside world... Just
--link the Xbus container (single host) or use an ambassador pattern (cluster).
This is really important to understand. PostgreSQL is configured to trust everyone so better keep it firewalled. And before yelling madness please consider this: If someone gains access to your host and is able to launch a container and open a port for himself he's got your data anyways... he's on your machine. So keep that port closed and secure your host. Your database is as safe as your host is, no more.
To prevent any data corruption during an image build, we use SHA256 algorithm to check file integrity of xbus archive and python requirement packages hosted on our repository.