Re: [sword-devel] SWORDWeb Docker image

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

Re: [sword-devel] SWORDWeb Docker image

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.

Re: [sword-devel] SWORDWeb Docker image

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

[sword-devel] SWORDWeb Docker image

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:

Re: [sword-devel] Uncategorised pages in our developers' wiki

I've since categorized 8 of those 10 pages. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Uncategorised-pages-in-our-developers-wiki-tp4656885p4656902.html Sent from the SWORD Dev mailing list archive at Nabble.com.

Re: [sword-devel] diatheke search type regex and the dot ?

Corrigendum: "everything outside ASCII" -- View this message in context: http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656901.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel

Re: [sword-devel] diatheke search type regex and the dot ?

Thanks Troy, The precise /flavour/ of *regex* supported by diatheke search really needs to be properly documented. Expecting the *dot* to be a byte when we're handling Unicode is just not on at all. I'm struggling more because I'm on Windows, where the UTF-16 verse UTF-8 disparity affects