Georg, Like you noticed and like Jim mentioned, the server will pick up on the domain you are using, but the actual URI structure is "fixed". You are supposed to be able to change the mount points for the various server components, by setting these properties in your server config:
org.neo4j.server.webadmin.data.uri=/db/data/ org.neo4j.server.webadmin.management.uri=/db/manage/ But I just tried it out, and there seems to be some sort of problem with it. I am investigating it, will commit a patch to fix whatever might be wrong. That said, I would recommend you not to mix the URIs of multiple applications this way. Although it is for sure possible and not necessarily a bad idea, unless there is some special reason for doing it, it is a lot less painful to use subdomains. That way you separate your infrastructure, making it a breeze to do things like fanning out your applications onto multiple servers, or adding various supporting HTTP layers and so on in the future. Cheers! Jacob On Thu, Apr 14, 2011 at 4:06 PM, Georg Summer <georg.sum...@gmail.com>wrote: > so in theory if I changed the proxy settings to: > > ProxyPass / http://<ip>:7474 > ProxyPassReverse / http://<ip>:7474 > > and reverse the neo4j-server.properties to the original state should work > out. (To answer that myself: yes it does) > > Any idea how I could configure these proxy settings in a nicer way so that > I > am still able to access the other sides on the apache? e.g. phpmyadmin > > On a side node: I am doing this dance because I like the Browser and it > would be perfect for a specific part of my concept. I do not know the > complete structure, but in theory it should be possible to rib out the > html/java script of the browser and just dump them in /var/www/neo_browser? > > Georg > > On 14 April 2011 14:56, Jim Webber <j...@neotechnology.com> wrote: > > > Hi guys, > > > > > Jim, what is your RESTy expertise on this? > > > > Our JAX-RS plumbing will dispatch on very specific parts of the URI > (that's > > just the way JAX-RS works). So if ultimately you send the server > something > > that doesn't match, it's either going to cause a 404 or similar, or where > we > > think it's sensible it'll cause a redirect to webadmin. > > > > So the only solution is to preserve the URI structure on the way into the > > Noe4j server, and (potentially) have it mapped to something else on the > > network where your client lives. > > > > Jim > > _______________________________________________ > > Neo4j mailing list > > User@lists.neo4j.org > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Jacob Hansson Phone: +46 (0) 763503395 Twitter: @jakewins _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
