Currently the optimize directory is not configurable. This can cause issues with some deployment systems that require the distributed code to be read-only. We should make this directory configurable so that you can point it at something like /tmp/kibana. While the optimize.bundleDir flag exists, it is not supported or documented, and doesn't work on built distributions
rashidkpc
All 7 comments
Nathan pinged me at the Elastic{ON} AMA booth, tthis would be really nice to have
rashidkpc
on 19 Feb 2016
Our use case is running multiple instances off the same /opt/kibana install. Currently the bundles will overwrite other instances.
pemontto
on 22 Feb 2016
We have multiple kibana 4.5 instances on a single server running the same code in /opt/kibana behind an nginx as reverse proxy. It' would be perfect to have an option to separate the optimize directory.
+1
xpatux
on 4 May 2016
+1
psaiz
on 9 Feb 2017
Any movement on this?
pemontto
on 4 Mar 2017
+1
gregwjacobs
on 8 Jun 2017
+1
emanzaman
on 18 Apr 2018
Related issues
ynux
路
3Comments
timroes
路
3Comments
bhavyarm
路
3Comments
spalger
路
3Comments
stacey-gammon
路
3Comments
Most helpful comment
We have multiple kibana 4.5 instances on a single server running the same code in /opt/kibana behind an nginx as reverse proxy. It' would be perfect to have an option to separate the optimize directory.
+1