very good Vincent, and yes Jena/Fuseki is indeed a great foundation for any
LOD project. the good news is that you already use shiro by virtue of
running fuseki.
I highly recommend you take a look at the fuseki UI. you can simply edit
the shiro.ini in the fuseki_run folder. just comment out
Thanks Marco!
My use case is very simple : I'm building a sample dataset with RDF data
from http://data.bnf.fr + a kind of "php-fuseki sandbox" where the user
will find examples of queries and php functions that show to reuse the
data. There also will be a small visualization library
Thanks Marco.
It seems to be mapped /$/server and AFAICS has not been mapped to
/$/status., only mentioned in shiro.ini.
Easy enough to add a second servlet-mapping if that's what people want
(the difference is that by default, /$/status is acess to anon and
/$/server is accessible only to
since Andy already explained the mechanics here I just wanted to add that
curl -uadmin: http://localhost:3030/$/server
gives you some of the information you are looking for. not sure what your
use case is but owner of PID is not expose.
On Fri, Nov 23, 2018 at 8:04 AM Vincent Ventresque <
just went back to 3.4 and it did not work. now upgraded to 3.9 to no avail
of status.
/$/stats works well though
since there is no action URL mapping in the web.xml for status I presume
that /$/status = anon is a typo in shiro.
On Thu, Nov 22, 2018 at 11:44 PM Andy Seaborne wrote:
> Do you
On 23/11/2018 08:03, Vincent Ventresque wrote:
Hello Andy & Marco
Can you explain `curl -u admin:` ? I've just looked at
That's curl-speak for setting user and password for HTTP basic
authentication.
Marco has Fuseki (full, using Shiro) set up with user/password control.
All the
Hello Andy & Marco
Can you explain `curl -u admin:` ? I've just looked at
I get a 404 when I go there :
http://jena.apache.org/documentation/fuseki2/admin.html
(there's a link to this page here :
http://jena.apache.org/documentation/fuseki2/fuseki-server-protocol.html)
Thanks in
Do you happen to know in which version it last did work?
Andy
On 22/11/2018 23:23, Marco Neumann wrote:
while you are at the fuseki status here
when accessing /$/status I am not getting no results on a Fuseki - version
3.8.0 instance with an enabled admin console
curl -u admin:***
while you are at the fuseki status here
when accessing /$/status I am not getting no results on a Fuseki - version
3.8.0 instance with an enabled admin console
curl -u admin:*** http://localhost:3030/$/status
get's me a 404 while I can see the results and stats in the web admin.
On
Hi Andy,
Thanks a lot for the explanation! I'm going to have a look at the script.
Anyway, since I'm not able to know how the user started the server, it
seems that I have to combine ps and netstat (if netstat provides useful
information about the server, it may be interesting to inform the
Hi Vincent,
The script "./fuseki" runs Fuseki as an OS service, and it is a wrapper
around "java -jar fuseki-server.jar". It is the script that records the
process id and makes OS tools concerned with OS services know about
Fuseki. If you run the server directly then there isn't a record of
Hello,
I use Fuseki via command-line tools in a PHP project, so I made a small
'wrapper' to call ruby & sh scripts via php : it enables to send queries
and process the results without using a RDF library such as EasyRDF.
I'm currently writing a code for a "sandbox environment" based on the
12 matches
Mail list logo
