Kibana: Deploy without Ruby / Warbler / Gems / Java etc

In Kibana 3, it was possible to deploy Kibana as a set of static files.

In Kibana 4, the default mode is to deploy using a full stack of Ruby code
on top of Warbler and JRuby etc.

It seems from my experimentation that this is not really required beyond

  • automatically populating the /config endpoint with some configuration
    settings
  • creating an Elasticsearch proxy (presumably to avoid dealing with CORS
    and XSS limitations)
  • enumerating plugins

(for reference I got Kibana 4 working in a static deployment by fixing a
few pathing issues and adding CORS support to ES)

While having a preconfigured stack that launches from a single command is
awesome, it also bloats the deployment requirement for more sophisticated
deployment.

What I'd like to know is if the general development direction is that more
dynamic configuration will be done in the Ruby code - creating an ever
increasing requirement on the Ruby stack in the future?

e.g. Generating a plugin manifest could easily be done using a bash / js
script - it does not need a full Ruby stack.

Thanks,

Ben

--
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/f316bdf1-01d4-4e20-8037-a36baf650263%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

As an Elasticsearch hosting provider, I share Ben’s questions here.

We currently host Kibana 3 for our customers alongside their hosted ES clusters. Our customers find this to be useful, since we’re able to offer a zero-deploy, zero-configuration experience that already handles all the CORS and authentication and such.

We’d like to continue providing that, and my current plan is to do a bit of work with Kibana 4 to extract the static assets, but it would be nice to get some official word from ES, Inc on the expected future trajectory for Kibana’s deployment story. A bit of consideration for static deploys would be really preferable to maintaining a de facto fork.

(Thanks for all the hard work, etc; I’m looking forward to getting Kibana 4 out the door on Bonsai!)

On Mon, Oct 27, 2014 at 11:54 PM, Ben Walding bwalding@cloudbees.com
wrote:

In Kibana 3, it was possible to deploy Kibana as a set of static files.
In Kibana 4, the default mode is to deploy using a full stack of Ruby code
on top of Warbler and JRuby etc.
It seems from my experimentation that this is not really required beyond

  • automatically populating the /config endpoint with some configuration
    settings
  • creating an Elasticsearch proxy (presumably to avoid dealing with CORS
    and XSS limitations)
  • enumerating plugins
    (for reference I got Kibana 4 working in a static deployment by fixing a
    few pathing issues and adding CORS support to ES)
    While having a preconfigured stack that launches from a single command is
    awesome, it also bloats the deployment requirement for more sophisticated
    deployment.
    What I'd like to know is if the general development direction is that more
    dynamic configuration will be done in the Ruby code - creating an ever
    increasing requirement on the Ruby stack in the future?
    e.g. Generating a plugin manifest could easily be done using a bash / js
    script - it does not need a full Ruby stack.
    Thanks,
    Ben
    --
    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/f316bdf1-01d4-4e20-8037-a36baf650263%40googlegroups.com.
    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/1414514591571.35f10e72%40Nodemailer.
For more options, visit https://groups.google.com/d/optout.