From 390154b91555b1138c943bcffb5d70e77e3d72d4 Mon Sep 17 00:00:00 2001 From: Noah Sprent <39567418+noahsprent@users.noreply.github.com> Date: Tue, 12 Aug 2025 20:50:44 +0100 Subject: [PATCH] Fix plugin/plugins typo --- .../06a-using-community-plugins.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/user-guide/03-Extending your Pioreactor/06a-using-community-plugins.mdx b/user-guide/03-Extending your Pioreactor/06a-using-community-plugins.mdx index 51ccb66fe..afbf09618 100644 --- a/user-guide/03-Extending your Pioreactor/06a-using-community-plugins.mdx +++ b/user-guide/03-Extending your Pioreactor/06a-using-community-plugins.mdx @@ -48,7 +48,7 @@ You can uninstall plugins from the same page, too. These will remove the action 2. To get this .whl file onto a Pioreactor, use either `scp`, WinSCP, or FileZilla. Note: if you upload the .whl file to your leader Pioreactor first, you can distribute the .whl file to all your workers with `pios cp ` 3. Once the .whl file is on the Pioreactor, use the following to install the plugin: ``` - pio plugin install --source + pio plugins install --source ``` For example: ``` @@ -57,4 +57,4 @@ You can uninstall plugins from the same page, too. These will remove the action ## Alternative: putting Python files in the the `plugins` folder -An alternative way to install a plugin is to place a Python file in the `/home/pioreactor/.pioreactor/plugins` directory on the Raspberry Pi. This is good for one-off scripts or plugins you are demoing or testing. See more [about writing and distributing plugins](/developer-guide/intro-plugins). \ No newline at end of file +An alternative way to install a plugin is to place a Python file in the `/home/pioreactor/.pioreactor/plugins` directory on the Raspberry Pi. This is good for one-off scripts or plugins you are demoing or testing. See more [about writing and distributing plugins](/developer-guide/intro-plugins).