Guide
How to install DSH plugins
Install DSH plugins by verifying the source, choosing the intended profile, reviewing the command as text, and testing the result in a reversible environment.
01
Choose a verified source
Start from the plugin repository or an upstream package link. A catalog name alone is not enough to infer an install package.
- Check repository ownership
- Read current installation notes
- Review recent maintenance
02
Install into the intended profile
Use the profile documented by the plugin and confirm every placeholder before running the command locally.
- Copying on this site does not execute
- Review package and version
- Keep the profile removable
03
Verify loading and rollback
Restart only if upstream requires it, inspect startup logs, exercise one documented capability, and remove the plugin if the profile becomes unstable.
- Keep exact logs
- Test one capability
- Record the uninstall path
Review sources
Sources help verify current facts. Their inclusion does not imply endorsement of this page.
install DSH plugins questions
What do I need before I install DSH plugins?
A working DSH setup, the package manager the plugin expects, and the repository URL. Take the install command from the repository rather than inferring it from a plugin name, so you do not install a similarly named package by accident.
Which profile should I install DSH plugins into?
One you can delete. A dedicated test profile lets you install, verify, and remove without touching the setup you work in every day.
Does copying a command on this site run it?
No. The copy button places text on your clipboard and does nothing else, so the command only runs when you paste it into your own terminal and press enter.
How do I verify the install worked?
Check the startup log for the plugin, then use one capability its documentation describes. A plugin needing an API key or config can install cleanly and still do nothing at all.
How do I remove a plugin cleanly?
Remove it from the profile, uninstall the package, and restart. If it wrote configuration or data files the repository should say where, and deleting the whole test profile is the reliable version of this.