You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.
Currently, you must run rm ~/.config/octant/plugins/<plugin name> to remove a plugin. It would be nice to be able to remove a plugin via the CLI instead so users don't have to remember the location of where plugin binaries are located.
The idea would be something along the lines of octant delete plugin <plugin name> would remove the plugin binary. Then that plugin will not be available when restarting Octant.
The text was updated successfully, but these errors were encountered:
Having some mechanism for getting at installed plugins is a good idea. I think having CLI commands could work, maybe in combination with having a button in Octant that opens the plugin folder using the system file browser.
@GuessWhoSamFoo Agreed. Something to also install plugins I think would be nice long term.
I think the CLI makes the most sense as the way for users to manage plugins since plugin changes require a restart anyway. Doing it through the UI might be misleading as to why something isn't added or removed.
We would like to remove having to restart to load/unload plugins as well #178 , which ties in to what @GuessWhoSamFoo is saying about having a good plugin story as part of our 1.0 roadmap.
Currently, you must run
rm ~/.config/octant/plugins/<plugin name>
to remove a plugin. It would be nice to be able to remove a plugin via the CLI instead so users don't have to remember the location of where plugin binaries are located.The idea would be something along the lines of
octant delete plugin <plugin name>
would remove the plugin binary. Then that plugin will not be available when restarting Octant.The text was updated successfully, but these errors were encountered: