From df1dc89ab08f79b64b320cf23ded03ca5e04fd84 Mon Sep 17 00:00:00 2001 From: KBbitsP <75751774+KBbitsP@users.noreply.github.com> Date: Thu, 17 Sep 2026 12:25:35 +0530 Subject: [PATCH] Correction to bash command Bash command was lost in black bg --- userguide/tutorials/plugin_installation.adoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/userguide/tutorials/plugin_installation.adoc b/userguide/tutorials/plugin_installation.adoc index ed73b2576..64651a827 100644 --- a/userguide/tutorials/plugin_installation.adoc +++ b/userguide/tutorials/plugin_installation.adoc @@ -16,14 +16,17 @@ Kill Bill scans the file system on startup and starts all the plugins that were [NOTE] ==== -The `/var/tmp/bundles` default applies to standalone (Tomcat/WAR) installations only. The official Kill Bill Docker images override this property to `/var/lib/killbill/bundles` (via the `KB_org_killbill_osgi_bundle_install_dir` environment variable). If you are running Kill Bill via Docker, always use `/var/lib/killbill/bundles` as the plugin installation path. You can verify the effective value for your container by running: +The `/var/tmp/bundles` default applies to standalone (Tomcat/WAR) installations only. The official Kill Bill Docker images override this property to `/var/lib/killbill/bundles` (via the `KB_org_killbill_osgi_bundle_install_dir` environment variable). If you are running Kill Bill via Docker, always use `/var/lib/killbill/bundles` as the plugin installation path. +==== + +You can verify the effective value for your container by running: [source,bash] ---- docker exec env | grep -i bundle ---- -==== + The directory structure looks like the following: