How to update installed version of kibana


#1

Hi, I've deployed Kibana, but I'd like to make a few tweaks to it. The geo tile map has support for circle markers and heat maps, but I would like to add lines connecting the points, if possible (I'm new to Leaflet as well, so we'll see how that goes)
But my problem is that kibana does not use the original javascript files (for example, src/ui/public/vislib/visualizations/marker_types/base_marker.js), but rather an optimized bundle.js. It isn't clear how to rebuild the optimize/bundles/kibana.bundle.js file.
Could anyone point me in the right direction? If possible, I'd like to avoid having to build kibana from source - I just want to modify the files in a deployed kibana instance and regenerate the kibana.bundle.js file.

Thanks


(Mark Walkom) #2

That would make an amazing PR if you wanted to contribute it back to the community :smiley:


(Spencer Alger) #3

Take a look at https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md for instructions on how to setup a Kibana development environment. The version of kibana that people download from elastic.co is built using the source code in that repository, so changes happen there and then can be used to make another build.


#4

I took a look at the contributing.md file, but is there any alternative to having to build Kibana from source? I just want to make a few tweaks to the javascript files and package everything up. It looks like some sort of minify-type library is used to compress all the javascript classes into a single kibana.bundle.js, but I don't know how to run just that without doing a full "npm install"on the kibana source.

Thanks


#5

The problem with the npm install is that the gridster dependency hangs. If I take it out, "npm install" completes ok. Here's what I get in the output if gridster 0.5.6 is a kibana dependency:
npm info attempt registry request try #1 at 9:20:00 AM
npm http request GET https://registry.npmjs.org/gridster
npm http 304 https://registry.npmjs.org/gridster
npm info attempt registry request try #1 at 9:20:01 AM
npm http request GET https://registry.npmjs.org/fsevents
npm http 304 https://registry.npmjs.org/fsevents
npm info git [ 'config', '--get', 'remote.origin.url' ]
npm info git [ 'fetch', '-a', 'origin' ]
npm info git [ 'rev-list', '-n1', '2.0.3' ]
npm info git [ 'clone',
npm info git '/home/user/.npm/_git-remotes/git-https-github-com-jquery-jquery-git-2-0-3-73adec7e',
npm info git '/tmp/npm-4290-7ef3172e/git-cache-54d9485c/f852e631ba85af7da4ad7594785e122504e7b233' ]
npm info git [ 'checkout', 'f852e631ba85af7da4ad7594785e122504e7b233' ]
npm info git [ 'submodule', '-q', 'update', '--init', '--recursive' ]

I'm assuming other people are able to build kibana fine - any idea what could be causing this?
Thanks


(system) #6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.