I have a collection of various demonstrators that make use of fuseki-server. Each requires essentially the same config file to configure the various services, differing only in the tdb store location.
Currently it’s either/or: use a config file or use --loc on the command line, but not both. It would be great to be able to override the location from the command line. In that way, I can provide a single config file along with instructions for each demo that include a location override. Interestingly, one can specify locations both using --loc and in the config file; the store gets created, but rather than fuseki-server using it, this message is displayed and fuseki-server terminates: "Dataset specificed on the command line and also a configuration file specificed.” (note misspelling of “specified”) This happens whether the store spec is included in the config file or when a config file is used but a location is not specified there. (I also noticed that, contrary to the instructions page, referencing a non-existing location from the command line triggers an error). Would it be at all possible to have the --loc be interpreted as a location override? I case you’re wondering why I don’t just provide a customized config file for each demo, it’s because my employer’s attorneys won’t allow us to distribute files that contain license restrictions. For the conf file case, the line # Licensed under the terms of http://www.apache.org/licenses/LICENSE-2.0 causes the proposed code distribution to be rejected. :-S As such, I need to generate a patch file for each config file.
