# Turn off Kibana Plugin Cache

**URL:** <https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521>\
**Category:** Kibana\
**Created:** [February 11, 2016, 4:44pm UTC](https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521 "2016-02-11T16:44:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lantern77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lantern77/32/22043_2.png) [@lantern77](https://discuss.elastic.co/u/lantern77)\
**Post date:** [February 11, 2016, 4:44pm UTC](https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521/1 "2016-02-11T16:44:54Z")

</div>

Hello,  
I am currently working with a kibana 4.2.1 production environment and was wondering if there was anyway to disable kibana from caching plugins.

Reason: Testing small modifications to currently existing plugins

Regards

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [February 11, 2016, 6:02pm UTC](https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521/2 "2016-02-11T18:02:04Z")

</div>

Not using the build, I don't believe.

What you want to do is test your changes using the [dev environment](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#development-environment-setup), where the server would respond to changes as you make them.

If you're doing plugin development, you can take the final output and just put it into your `installedPlugins` path of your production build.

---

<div class="post-metadata">

**Author:** ![lantern77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lantern77/32/22043_2.png) [@lantern77](https://discuss.elastic.co/u/lantern77)\
**Post date:** [February 11, 2016, 6:30pm UTC](https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521/3 "2016-02-11T18:30:26Z")

</div>

Okay thanks,  
Is there many significant differences between the dev environment and the corresponding production version.

> **[elastic/kibana](https://github.com/elastic/kibana#installation)**
>
> kibana - :bar\_chart: Kibana analytics and search dashboard for Elasticsearch

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [February 11, 2016, 7:08pm UTC](https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521/4 "2016-02-11T19:08:15Z")

</div>

Not really. The server running in "dev mode" does some watching and automatic restarting, which makes development easier. It requires a lot more system resources though, so be aware of that. There's also some "dev" dependencies that'll be installed, and you'll need to bring your own node install.

Other than that though, it's pretty close to what we ship as a build.

---

<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, 2:02pm UTC](https://discuss.elastic.co/t/turn-off-kibana-plugin-cache/41521/5 "2017-07-06T14:02:30Z")

</div>