On 11 September 2015 at 09:29, Andy Seaborne <[email protected]> wrote:
> (hmm - ATM it is showing the old one. Are we seeing eventual consistency in > action as the builder sweeps around?) for the 2.3.0 tag I just updated my older "manual" approach - which uses a different base image without Maven. (as my PR is based on the latest master) I can make an alternative 2.3.0 based on the pull-request Maven approach if I back-date the <version> in the pom.xml - but I thought that would be a bit cheeky. You can test the Pull Request docker image as docker run stain/jena-fuseki:devel -- this would be using the 2.3.1-SNAPSHOT at the time of build. > There are 11 Fuseki's (some are Fuseki1) on hub.docker > > Are they all effectively the same? > Anything to learn from the others? > Better? Different? > > So there is a question of whether the community approach is better than a > single project form. Thoughts? Many of them are lacking documentation. Some are outdated. The better ones are focused on the Fuseki 1 approach of manually editing config files -- I think a main purpose of a Docker image is to quickly get started - it should work out of the box. This fits very well with Fuseki 2. In my approach I also included instructions on how to use the tdbloader as a way to populate the store. Once you need more heavy production usage of course you will want your own config files - so I don't think that should be 'hidden' - just left as a second step. It should be noted that last week or so the doc of https://hub.docker.com/r/stain/jena-fuseki/ broke all hyper links due to https://github.com/docker/hub-feedback/issues/195 :) I guess that's life in the fast lane.. I wouldn't want to stand here and say that what I cooked together is the Best And Only approach! There is also the issue of timing. When I made my Docker image, Fuseki 2 was still experimental, and there were no other Fuseki 2 images. But I think if the project takes ownership, then discussion about how Docker image should be and evolve can happen within the Jena community rather than as spread out comments on Alice' and Bob's private approaches. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
