Yes, docker just makes things easy to both get things up and running
quickly without worrying about dependencies, or to spin up swordweb as a
service in a fault-tolerant / load-balanced cluster using something like
kubernetes.
Greg has optimized my Dockerfile to make it generate an image
Troy and I were musing about this last week. He pointed out that there are
frequent requests for SwordWeb functionality on another host. This appears to
make it much simpler to get it up and running.
DM
> On Mar 5, 2017, at 1:00 PM, David Haslam wrote:
>
> I expect I'm
I expect I'm not the only list member that had to go and find out what on
earth Troy was talking about when he used the word "docker".
https://www.docker.com/
Even so, it would help to know a bit more on how Troy sees this advance the
aims of CrossWire.
Best regards,
David
--
View this
I hadn't tried it, as I was on my phone responding to your initial email.
The Docker hub has the direct ability to build things easily off of a
linked repository. I just went through setting that up last week for an
image I'm using to test stuff at work. So getting automated builds without
needing
We're not building with automation yet. This is just a first attempt to make it
work. The Dockerfile is committed in the swordweb repo but there are files that
need to be built from SWORD (swordorbserver) and copied to the docker-template
folder in swordweb before the Dockerfile can be used.
Where is the repository with the Dockerfile? What triggers updates and
rebuilds of the container?
On Mar 4, 2017 7:05 PM, "Troy A. Griffitts" wrote:
> I've compiled a docker image for SWORDWeb if anyone is interested in
> trying it out. If you have docker installed
I've compiled a docker image for SWORDWeb if anyone is interested in
trying it out. If you have docker installed (should work on mac,
windows, and linux), and you'd like to, e.g., expose your SWORD modules
installed in /home/me/.sword on port you can try with a command
like this: