Re: [Neo4j] [neo4j] Exposing Webadmin
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.comwrote: 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
Re: [Neo4j] [neo4j] Exposing Webadmin
Looked over the configuration properties I mentioned, and it seems I was incorrect, am unable to reproduce the problems I saw before. Doing something like: org.neo4j.server.webadmin.management.uri=/asd/ Will make the server move management stuff to that URI, and webadmin will follow suit. So for your case, you should be able to do: org.neo4j.server.webadmin.data.uri=/neo4jdb/db/data/ org.neo4j.server.webadmin.management.uri=/neo4jdb/db/manage/ I still do not recommend doing this :) There are plans for features in the next release (1.4) that would mean we need to make backwards-incompatible changes to these configuration directives that will break this setup. :( /Jacob On Mon, Apr 18, 2011 at 11:24 AM, Jacob Hansson ja...@voltvoodoo.comwrote: 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.comwrote: 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 -- Jacob Hansson Phone: +46 (0) 763503395 Twitter: @jakewins ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] [neo4j] Exposing Webadmin
Hey Jake, [with my RESTafarian hat on] Will make the server move management stuff to that URI, and webadmin will follow suit. So for your case, you should be able to do: org.neo4j.server.webadmin.data.uri=/neo4jdb/db/data/ org.neo4j.server.webadmin.management.uri=/neo4jdb/db/manage/ I still do not recommend doing this :) Why not? I thought Webadmin just cares about URIs from the discovery document, and not so much about their actual structure (since we're trying hard to be Web-friendly). Jim ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] [neo4j] Exposing Webadmin
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
Re: [Neo4j] [neo4j] Exposing Webadmin
Georg, mmh! I could try setting this up on my local machine, but is anyone else having input here? Seems like we should examine the Webadmin Javascript requests. Can you access the data REST endpoint with curl? 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 12:50 PM, Georg Summer georg.sum...@gmail.com wrote: Hi there, My setup is that I have a server in a subnet protected by relative strict port policy, so I can not access the 7474 port of the server where by default neo4j is running. I have an Apache Server running as well serving some websites. I am accessing it remotely from a different part of the network. Checking the documentation showed that I can use a proxypass to expose the restful service: ProxyPass /neo4jdb/db http://localhost:7474/db ProxyPassReverse /neo4jdb/db http://localhost:7474/db which works fine. (at least using it through a browser for querying) So my idea was: same thing for the webadmin: ProxyPass /neo4jdb/webadmin http://localhost:7474/webadmin ProxyPassReverse /neo4jdb/webadmin http://localhost:7474/webadmin I get directed to the webadmin page. The side gets displayed but no values are retrieved so all status info is undefined. The Browser also only tells me: not found. The Service Info displays: no bean found # REST endpoint for the data API # Note the / in the end is mandatory #org.neo4j.server.webadmin.data.uri=/db/data/ org.neo4j.server.webadmin.data.uri=http://localhost/neo4jdb/db/data/ # REST endpoint of the administration API (used by Webadmin) #org.neo4j.server.webadmin.management.uri=/db/manage/ org.neo4j.server.webadmin.management.uri=http://localhost/neo4jdb/db/manage/ That didn't work. I also tried directly the IP address of the machine. as well as: org.neo4j.server.webadmin.data.uri=http://localhost:7474/db/data/ org.neo4j.server.webadmin.management.uri=http://localhost:7474/db/manage/ no luck either. Any Idea what I am missing? regards, Georg ___ 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
Re: [Neo4j] [neo4j] Exposing Webadmin
Yeah Curl works fine; as well as from a Browser;
curl http://server-ip/neo4jdb/db/manage/
{
services : {
console : http://server-ip/db/manage/server/console,
jmx : http://1server-ip/db/manage/server/jmx,
monitor : http://server-ip/db/manage/server/monitor
}
}
what I just noticed is that the links here can not work because they are
missing my /neo4jdb/
Is that a problem with the proxy settings?
Georg
On 14 April 2011 13:08, Peter Neubauer peter.neuba...@neotechnology.comwrote:
Georg,
mmh! I could try setting this up on my local machine, but is anyone
else having input here? Seems like we should examine the Webadmin
Javascript requests.
Can you access the data REST endpoint with curl?
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 12:50 PM, Georg Summer georg.sum...@gmail.com
wrote:
Hi there,
My setup is that I have a server in a subnet protected by relative strict
port policy, so I can not access the 7474 port of the server where by
default neo4j is running.
I have an Apache Server running as well serving some websites.
I am accessing it remotely from a different part of the network.
Checking the documentation showed that I can use a proxypass to expose
the
restful service:
ProxyPass /neo4jdb/db http://localhost:7474/db
ProxyPassReverse /neo4jdb/db http://localhost:7474/db
which works fine. (at least using it through a browser for querying)
So my idea was: same thing for the webadmin:
ProxyPass /neo4jdb/webadmin http://localhost:7474/webadmin
ProxyPassReverse /neo4jdb/webadmin http://localhost:7474/webadmin
I get directed to the webadmin page. The side gets displayed but no
values
are retrieved so all status info is undefined. The Browser also only
tells
me: not found.
The Service Info displays: no bean found
# REST endpoint for the data API
# Note the / in the end is mandatory
#org.neo4j.server.webadmin.data.uri=/db/data/
org.neo4j.server.webadmin.data.uri=http://localhost/neo4jdb/db/data/
# REST endpoint of the administration API (used by Webadmin)
#org.neo4j.server.webadmin.management.uri=/db/manage/
org.neo4j.server.webadmin.management.uri=
http://localhost/neo4jdb/db/manage/
That didn't work. I also tried directly the IP address of the machine. as
well as:
org.neo4j.server.webadmin.data.uri=http://localhost:7474/db/data/
org.neo4j.server.webadmin.management.uri=
http://localhost:7474/db/manage/
no luck either.
Any Idea what I am missing?
regards,
Georg
___
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
Re: [Neo4j] [neo4j] Exposing Webadmin
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
Re: [Neo4j] [neo4j] Exposing Webadmin
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
