[sword-devel] Docker ?
chris at burrell.me.uk
Sun Dec 31 05:06:09 MST 2017
In a nutshell, docker is a way of packaging up software so that it can be
re-used. One of the main reasons for using it is to faciliate deployment.
E.g. using infrastructure schedulers such as Kubernetes, ECS, Mesos, Docker
swarm (there are more), you can then instruct the scheduler to download a
particular docker image and run it (say on 2 different servers and into 2
different geographical locations). The scheduler is then responsible for
maintaining the current number of desired docker instances up via health
checks. So for example it may destroy and re-run a docker image if it
believes that something is unhealthy.
In the context of CrossWire, I suspect you would need to ensure that the
data is packaged within the docker image (or you can virtually mount a
local hard-drive). However, I've seen very little use for it for end-user
type applications. It is generally (at the moment) more orientated towards
developers. So for example, you could package the OSIS tools, the diatekhe,
etc. so that it doesn't require any installation requirements on
Windows/Linux/etc. All is transparent. Doing it for a front-end installed
on a desktop has limited use IMHO.
My two pennies.
On 30 December 2017 at 19:26, David Haslam <dfhdfh at protonmail.com> wrote:
> In a separate thread, DM wondered whether Docker
> <https://en.wikipedia.org/wiki/Docker_(software)> might be a way forward.
> *I know virtually nothing about it, save what I can read quickly.*
> Let's hear from developers the pros and cons in the context of what we do
> in CrossWire.
> Best regards,
> Sent with ProtonMail <https://protonmail.com> Secure Email.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel