# \[ANNOUNCE\] kibana-rack 0.1.4 released

**URL:** <https://discuss.elastic.co/t/announce-kibana-rack-0-1-4-released/19290>\
**Category:** Elasticsearch\
**Created:** [August 14, 2014, 4:24pm UTC](https://discuss.elastic.co/t/announce-kibana-rack-0-1-4-released/19290 "2014-08-14T16:24:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tony\_Burns](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tony_burns/32/1338_2.png) [@Tony\_Burns](https://discuss.elastic.co/u/Tony_Burns)\
**Post date:** [August 14, 2014, 4:24pm UTC](https://discuss.elastic.co/t/announce-kibana-rack-0-1-4-released/19290/1 "2014-08-14T16:24:37Z")

</div>

I just released version 0.1.4 of kibana-rack ([https://github.com/tabolario/kibana-rack](https://github.com/tabolario/kibana-rack))! This release has a set of fixes and refinements to the Elasticsearch proxy, thanks to @dcarley. Notably, proxying to the internal Kibana index is now working.

If you use Elasticsearch in your Rack/Rails application, check out kibana-rack for an easy way to deploy Kibanafor exploring your Elasticsearch indexes!

Full changelog at [https://github.com/tabolario/kibana-rack/releases/v0.1.4](https://github.com/tabolario/kibana-rack/releases/v0.1.4)

Cheers!

Tony

--  
Tony Burns  
Operations Engineer / Software Developer  
Quad Learning, Inc.  
@tabolario on GitHub and Twitter

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:08am UTC](https://discuss.elastic.co/t/announce-kibana-rack-0-1-4-released/19290/2 "2017-07-06T01:08:29Z")

</div>

Closed on July 6, 2017, 1:08am UTC


