# Build WITH plugins included **URL:** \ **Category:** Kibana\ **Created:** [March 9, 2017, 4:13pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017 "2017-03-09T16:13:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Kikketer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kikketer/32/13813_2.png) [@Kikketer](https://discuss.elastic.co/u/Kikketer)\ **Post date:** [March 9, 2017, 4:13pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017/1 "2017-03-09T16:13:18Z")
I'm using a forked version of Kibana since we have a few changes for both our build process and theming. Anyway, I would like to get the `kibana-5.2.0-linux-x86_64.tar.gz` file with the plugins installed already. I need this file with the plugins installed because our build and deployment process shouldn't/can't install plugins after kibana is deployed and running. So I run the `./bin/kibana-plugins install` script with the zip files of all the plugins I've created during the build process. I then run `npm build` on Kibana. Unfortuantely that build process produces the `kibana-5.2.0-linux-x86_64.tar.gz` file but the `/plugins` folder is empty. I'm currently working through running the plugins-install script, copy out the items in `/plugins`, run `npm build` then extracting and reinjecting the plugins, THEN re-compressing. Obviously this is quite the laborus thing to do but it's automated. What I fear however is if the plugins continue to not work means that the `npm build` scripts modify more things (and thus are ignoring things) that are related to the plugin installs instead of just creating optimized versions of the plugins in the `/plugins` folder. Is anyone in Elastic or here aware of what other things the `npm build` does that makes it ignore the plugins folder? And what does the `kibana-plugins install` script do besides optimize the items in the `/plugins` folder? Hope that makes sense. ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [March 9, 2017, 5:59pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017/2 "2017-03-09T17:59:03Z")
Since you are operating a fork you will need to create the package with `npm build`, extract the resulting tar and install your plugins. If you need to re-distribute as a tar file simply retar the directory. ---
**Author:** ![Kikketer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kikketer/32/13813_2.png) [@Kikketer](https://discuss.elastic.co/u/Kikketer)\ **Post date:** [March 9, 2017, 6:00pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017/3 "2017-03-09T18:00:22Z")
Awesome, that's exactly what my next move was going to be 🙂 Thanks ---
**Author:** ![Kikketer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kikketer/32/13813_2.png) [@Kikketer](https://discuss.elastic.co/u/Kikketer)\ **Post date:** [March 9, 2017, 7:53pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017/4 "2017-03-09T19:53:52Z")
This procedure worked, thank you! It as a lot easier than I expected and was attempting before. ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [March 9, 2017, 8:39pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017/5 "2017-03-09T20:39:42Z")
@Kikketer, good to hear! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 6, 2017, 8:39pm UTC](https://discuss.elastic.co/t/build-with-plugins-included/78017/6 "2017-04-06T20:39:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.