[
https://issues.apache.org/jira/browse/JENA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997109#comment-16997109
]
Andy Seaborne commented on JENA-909:
------------------------------------
bq. What do you mean with "container namespace"? The container filesystem?
Yes
bq. Why not pass -loc $DATA to the entrypoint by default?
You can pass {{--loc}} -- it is the database as per normal command line Fuseki.
And you can import a database by placing it under $DATA before starting Docker
- that's one part of why it is a mount point, the other being so that it does
not go away when the container does.
A mount point is {{--mount}} to the docker run. Isn't that what you want?
The $DATA gives the user the chance to a single "/var/fuseki" in the container.
There isn't a prescriptive layout under that but the "$DATA/data" for the
database and /logs for logs, with config at he top level is one way. If it is
for multiple databases, add a level of "database name".
One use is configs in "/var/fuseki", databases under "/var/fuseki/data"
Loading every time at scale will be slow.
Loading small data is a test requirement and it can also be done by POSTing the
data to the dataset after launch.
No Dockerfile will address all use case for test and deployment. The idea is to
offer a simple one to get people started.
There can be several in the codebase if they address common use cases. But when
a user wants a high degree of control, they will want to have their own with
the exact setup they want.
> Create Docker launcher for Fuseki
> ---------------------------------
>
> Key: JENA-909
> URL: https://issues.apache.org/jira/browse/JENA-909
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Andy Seaborne
> Priority: Major
> Attachments: Dockerfile.0, image-2019-10-02-22-24-12-723.png,
> log4j.properties
>
>
> Provide a Docker launcher and setup documentation for Fuseki2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
