Dear everyone,<br><br>I've updated the installation bundle for SemanticXO and also fixed a few bugs reported on this mail thread.<br>To play around with the code:<br>* go to <a href="http://git.sugarlabs.org/semanticxo/main/trees/master/patch_my_xo">http://git.sugarlabs.org/semanticxo/main/trees/master/patch_my_xo</a><br>
* put the files "patch_my_xo.py" and "semanticxo.tgz" somewhere on the XO<br>* login as root, set patch_my_xo.py to be executable and type "./patch_my_xo.py setup"<br>* reboot<br><br>It's a very harsh script that will just overwrite the standard Journal code and erase all the content. I've tested it on a couple of XO-1. If everything works fine, you won't see any difference.<br>
To see what happens in the back-end, open a web browser to http://<IP_OF_THE_XO>:8080 to see the content of the triple store.<br><br>I'd now like to implement something to remotely query an XO triple store from an activity. <br>
Does anyone know if it is possible to get an IP of a neighbour returned by the presence service?<br>Or, shall I better wrap external calls to the triple store in a DBus API, even if that is all plain HTTP?<br><br>Christophe<br>
<br><div class="gmail_quote">On 2 July 2012 17:38, Christophe Guéret <span dir="ltr"><<a href="mailto:c.d.m.gueret@vu.nl" target="_blank">c.d.m.gueret@vu.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Aleksey,<br><div class="gmail_quote"><div class="im"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've packaged redstore to SD:Factory repos<br>
(<a href="https://packages.sugarlabs.org/project/monitor?project=SweetsDistribution:Factory" target="_blank">https://packages.sugarlabs.org/project/monitor?project=SweetsDistribution:Factory</a>)<br>
the package is "redstore" that provides "redstore" command and<br>
"redstored" init.d script.</blockquote></div><div>Great! Many thanks :)<br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I didn't make it autorun in case if you will use it in<br>
the same way as Journal (and Sugar Network database), i.e., keep<br>
database in ~/.sugar/<PROFILE> and start daemon from current user's<br>
session.<br></blockquote></div><div>Could you point me to an example on how to set this up?<br>Currently I set the database system wide and start the daemon at boot time but switching to a user session would make sens.<br>
</div><div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
btw, it might be useful to create SemanticXO package as well and make it<br>
pluggable like it was done with Sugar Network (checkbox in "Sweets<br>
Distribution" Control Panel component). i.e., it should regular DBus<br>
service that provides the same Dbus API as sugar-datastore. If you will<br>
do that, I think it will be possible to plug either sugar-datastore or<br>
SemanticXO in runtime.<br></blockquote></div>It is already the case, on my test machines I remove sugar-datastore to put the one provided by SemanticXO instead.<br>That one uses the same DBUS API and service name. I will look into packaging it.<br>
<br>I was slowed down on SemanticXO recently, I hope to be able to get back in speed soon...<span class="HOEnZb"><font color="#888888"><br><br>Christophe<br><br><br><br><br><br></font></span></div>
</blockquote></div><br>