Georg, yes, the Webadmin part of Neo4j is a standalone app that only needs the initial pointer to the server management endpoint, so you should be able to put it somewhere else if you can initialize it correctly (Firebug is your friend)
Also, it is built from Coffeescript with a maven plugin that Jake wrote, so you might keep that step as is and only copy over the resulting javascript artifacts somewhere else. Otherwise, maybe we could add an explicit override of the server URL base endpoint in neo4j-server.properties in order to cover for these proxying scenarios when generating the server REST enpoints, Jim? Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. 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 > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
