Skip to content

Commit 69311d0

Browse files
Merge pull request #56 from noahsprent/fix_plugin_typo
Fix plugin/plugins typo
2 parents 549ea05 + 390154b commit 69311d0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

user-guide/03-Extending your Pioreactor/06a-using-community-plugins.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ You can uninstall plugins from the same page, too. These will remove the action
4848
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 <location of .whl file>`
4949
3. Once the .whl file is on the Pioreactor, use the following to install the plugin:
5050
```
51-
pio plugin install <name-of-plugin> --source <location of .whl file>
51+
pio plugins install <name-of-plugin> --source <location of .whl file>
5252
```
5353
For example:
5454
```
@@ -57,4 +57,4 @@ You can uninstall plugins from the same page, too. These will remove the action
5757

5858
## Alternative: putting Python files in the the `plugins` folder
5959

60-
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).
60+
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).

0 commit comments

Comments
 (0)