[
https://issues.apache.org/jira/browse/JENA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065718#comment-15065718
]
Andy Seaborne edited comment on JENA-1101 at 12/20/15 11:25 AM:
----------------------------------------------------------------
Fuseki runs on different Linux distros, on OS/X and MS Windows.
The default setup needs to be easy for common use case of a user, who is not an
experienced system admin and wants to a simple "unpack and go". Addressing
this, reduces the support costs on the project.
>From that default, system admins can craft their specific needs for a service
>by setting the environment variables and using symbolic links.
What would be useful is documentation that describes how to set
{{/etc/default/fuseki}} and to put in symbolic links to provide a layout that
meets other needs. A set of guidelines for Centos would be good to have; that
could even include a script to perform the operations.
That seems to me to be a way to get the effect you want without writing and
maintaining a installers.
was (Author: andy.seaborne):
Fuseki runs on different Linux distros, on OS/X and MS Windows.
The default setup needs to be easy for common use case of a user, who is not a
experienced system admin and wants to "unpack and go". Addressing this reduces
the support costs on the project.
>From that default, system admins can craft their specific needs for a service
>by setting the environment variables and using symbolic links.
What would be useful is documentation that describes how to set
{{/etc/default/fuseki}} and to put in symbolic links to provide a layout that
meets other needs. A set of guidelines for Centos would be good to have; that
could even include a script to perform the operations.
That seems to me to be a way to get the effect you want without writing and
maintaining a installers.
> Fuseki filesystem layout and Linux FHS
> --------------------------------------
>
> Key: JENA-1101
> URL: https://issues.apache.org/jira/browse/JENA-1101
> Project: Apache Jena
> Issue Type: Improvement
> Affects Versions: Fuseki 2.3.1
> Reporter: Joachim Neubert
>
> When it comes to filesystem layout, the Java/Tomcat/Webapps world differs
> quite fundamentally from the Linux world: Whereas for Tomcat or Fuseki it is
> quite normal to have all files under a common root directory, the [Linux
> Filesystem Hierarchy
> Standard|https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard] (which
> is followed by most distributions) provides multiple roots for application
> files:
> Configuration goes to /etc, read-only files to /usr, variable files to /var
> (./log, ./cache etc.). To give you a better idea what this means in practice,
> I add the layout of the tomcat installation by Centos 7 RPM as an example.
> From a linux sysadmins point of view, this makes it easy to know where to
> find stuff without any special knowledge of the application, and to
> generalize tasks like backup (e.g. exclude all application cache files on the
> system).
> On the other hand, this means considerable more work, if you have to cover
> systems outside the Linux world too. Things may get even more complicated by
> remaining differeces between distributions and SElinux policies.
> So I don't suppose FHS compatibility is an realistic option for Fuseki.
> Yet, the current handling of mapping $FUSEKI_HOME/run to /etc/fuseki, with
> the whole bunch of assorted runtime files, feels profundly wrong. According
> to FHS, I would expect something like
> {noformat}
> etc/
> fuseki/
> config.ttl
> shiro.ttl
> conf.d/
> service1.ttl
> ...
> {noformat}
> and all the other stuff elsewhere.
> So I wonder if it would be possible to put the config hierarchy above under
> a, say, $FUSEKI_CONF root, which defaults to /etc/fuseki in the .war
> installation, and to $FUSEKI/conf otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
