Why is Kibana 4.0 no longer a status webapp?

Curious why Kibana 4.0 is no longer a static webap and why it requires a
Java daemon.

Is this strictly required? I guess I'm fine if it is but why? What does
the Java daemon provide?

I guess I liked that it was a static webapp as it allows for easier
integration on our end.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/eb9dfdf5-4bd4-41eb-bea7-0029d628ae29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

There's info from some of the devs in this thread -
https://groups.google.com/forum/?hl=en-GB#!searchin/logstash-users/kibana/logstash-users/X_ClBEKH6tk/L9z9i9BOFtUJ

On 1 December 2014 at 04:29, Kevin Burton burtonator@gmail.com wrote:

Curious why Kibana 4.0 is no longer a static webap and why it requires a
Java daemon.

Is this strictly required? I guess I'm fine if it is but why? What does
the Java daemon provide?

I guess I liked that it was a static webapp as it allows for easier
integration on our end.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/eb9dfdf5-4bd4-41eb-bea7-0029d628ae29%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/eb9dfdf5-4bd4-41eb-bea7-0029d628ae29%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZk%3DsXhnEXCZzXzThRnc9J_N0AYFkHN5WCk4w9VS%2B41KJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Curious why Kibana 4.0 is no longer a static webap and why it requires a
Java daemon.

Is this strictly required? I guess I'm fine if it is but why? What does
the Java daemon provide?

The Java daemon is just because it's a Ruby web application running with
JRuby. As the application is Rack-based, you can run it under any
Rack-compatible server if you're prepared to hack about with it.

From my experimentation I got it running under Apache & Passenger and
from what I can tell there's very little that is dynamic; it still is just
HTML/Javascript under the hood. There are a couple of URLs that are dynamic
although I'm not convinced they could be made static too.

It just comes with its own webserver to minimise the barrier to entry.

I put my findings and configuration here:

when I asked if it was possible.

I guess I liked that it was a static webapp as it allows for easier
integration on our end.

Same, I didn't want to run Yet Another Webserver that has fewer features,
etc. etc. and I liked how v3 was easy to deploy & integrate.

Matt

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/20141201100656.GD28742%40simulant.bodgit-n-scarper.com.
For more options, visit https://groups.google.com/d/optout.