I really like the idea of not giving webadmin "special keys", if that makes
sense. Keeping webadmin separate from the server apart from having its
static files served from there means we have to eat our own dogfood.
That said, webadmin needs to somehow figure out where to place that first
GET call
Hey Jake,
So would you be in favour of removing the discovery document in favour of a
server-generated index.html? Or perhaps making it richer (e.g. here's the
discovery document pertaining to this "host" header)?
Jim
___
Neo4j mailing list
User@lists
Oops, I realized I just lied.
Webadmin will not work if the *root URI of the domain it is accessed from
does not return the "discovery document"* that tells it where to find
management and database resources. We could work around this, for instance
by making webadmins index.html be generated by th
Hey jim, see inline response :)
On 2011 4 18 12:00, "Jim Webber" wrote:
>
> 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.da
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/
>
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
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.serv
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
so in theory if I changed the proxy settings to:
ProxyPass / http://:7474
ProxyPassReverse / http://: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
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 s
Mmh!
This might be the problem. The server is issuing these URLs, and has
no way of knowing that you did reverse proxy everything. This is an
interesting case.
Jim, what is your RESTy expertise on this?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +4
Yeah Curl works fine; as well as from a Browser;
curl http:///neo4jdb/db/manage/
{
"services" : {
"console" : "http:///db/manage/server/console",
"jmx" : "http://1/db/manage/server/jmx",
"monitor" : "http:///db/manage/server/monitor"
}
}
what I just noticed is that the links here
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
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
14 matches
Mail list logo