afs commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491888081
##########
File path: source/documentation/fuseki2/fuseki-webapp.md
##########
@@ -1,48 +1,71 @@
---
-title: Running Fuseki
+title: Running Fuseki with UI
---
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
* [As a standalone server](#fuseki-standalone-server)
* [As a service](#fuseki-service) run by the operation system, for example,
started when the machine
* [As a Web Application](#fuseki-web-application) inside a container such as
Apache Tomcat or Jetty
boots.
-* [As a configurable SPARQL server](#fuseki-main)
-* [As a deployment and development standalone server](#fuseki-server)
+
+Fuseki is also packaged as a plain server ["Fuseki Main"](fuseki-main.html)
+with no UI for use as a configurable SPARQL server, for [building as a Docker
+container](fuseki-docker.html), and as a deployment and development standalone
+server.
+
+Both packaging used the same configuration file format, and in standalone
server
+mode, the same command line arguments.
See "[Fuseki Configuration](fuseki-configuration.html)" for information on
-how to provide datasets and configure services.
+how to provide datasets and configure services usoing the configuration file.
## Fuseki as a Standalone Server {#fuseki-standalone-server}
This is running Fuseki from the command line.
- fuseki-server [--mem | --loc=DIR] [[--update] /NAME]
-
- fuseki-server --config=CONFIG
+To publish at <tt>http://<i>host</i>:3030/NAME</i></tt>:
where `/NAME` is the dataset publishing name at this server in URI space.
+TDB1 database:
+
+ fuseki-server [--loc=DIR] [[--update] /NAME]
+
The argument `--tdb2` puts the command line handling into "TDB2 mode".
A dataset created with `--loc` is a TDB2 dataset.
+TDB2 database:
+
+ fuseki-server --tdb2 [--loc=DIR] [[--update] /NAME]
+
+In-memory, non-peristent database (always updatable):
+
+ fuseki-server --mem /NAME
+
+Load a file at start and provide it read-only:
+
+ fuseki-server --file=MyData.ttl /NAME
+
+where "MyData.ttl" can be any RDF format, both triples or quads.
+
+Administrative functions are only avilable from "localhost".
Review comment:
Shiro!
##########
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##########
@@ -146,13 +173,15 @@ A GSP operation has `?default` or `?graph=`.
Quads operations have no query string and a have a `Content-Type` for a data in
a RDF triples or quads syntax.
+Quads operations only apply to requests sen tot he dataset URL.
Review comment:
(The statement isn't actually correct! I just tested it and quads work
on a named endpoint.)
##########
File path: source/documentation/fuseki2/fuseki-data-services.md
##########
@@ -17,7 +17,7 @@ update
GSP including direct naming for GSP
in addition:
-
+fuse
Review comment:
"fuseki-data-services" is linked to the documentation and it looks like
it has largely been overtaken. The bit about active/offline isn't accurate.
I'll delete "fuseki-data-services".
##########
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##########
@@ -121,6 +93,61 @@ without a configuration file is:
| `fuseki:upload` | HTML form file upload |
| `fuseki:no-op` | An operation that causes a 400 or 404 error |
+Custom extensions can be added (see [Programmatic
configuration](fuseki-main.html#build) of the Fuseki server). To be able to
uniquely identify the operation, these are usually
+
+ fuseki:endpoint [
+ fuseki:operation fuseki:shacl ;
+ fuseki:name "shacl" ;
+ ] ;
+
+See the section ["Integration with Apache Jena
Fuseki"](https://jena.apache.org/documentation/shacl/#integration-with-apache-jena-fuseki)
for details of the SHACL support. While this operation is part of the standard
Fuseki distribution, this operation is added during system initialization,
using the custom operation support.
Review comment:
Good point. We can make it
"/documentation/shacl/#integration-with-apache-jena-fuseki" . I like the rooted
path because if the Fuseki docs get structured in some way, the "external" link
will still work.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
