For enterprise deployment, Fuseki provides the standard option: a ordinary WAR file (packaged inside the distribution).
https://jena.apache.org/download/index.cgi --- A. Soroka The University of Virginia Library > On Sep 9, 2016, at 6:16 AM, otheus uibk <otheus.u...@gmail.com> wrote: > > Thanks Andy, > > An RPM for Fuseki is the goal. > >> If Fuseki, consider using one of the docker containers. > > I hoped you were joking with this. I had given it some thought, and for our > immediate purposes, this would suffice. Then again, so would a jar file run > out of a personal directory. For enterprise deployment in a productive > environment, this isn't helpful. > > On Thu, Sep 8, 2016 at 10:33 PM, Andy Seaborne <a...@apache.org> wrote: > >> For Fuseki/RPM, what you are trying to install is a directory hierarchy + >> maybe some setting in other files. So don't treat as a Java thing but pull >> the prebuilt zip and work with files from there. > > > Yeah, it's the "setting in other files" bit which is pretty critical. The > main thing is a set of service startup/stop scripts (or service files, if > systemd), and identifying package dependencies (java 1.7 OK? java 1.8 OK?). > > There's a maven plugin at http://www.mojohaus.org/rpm-maven-plugin/ but I > don't really understand how to use it. > > > -- > Otheus > otheus.u...@gmail.com > otheus.shell...@uibk.ac.at
