-
Notifications
You must be signed in to change notification settings - Fork 489
Installing a plugin requires restart of main octant process. #178
Comments
+1, This also makes plugin development a bit more painful, since I have to rebuild my plugin and restart Octant to see changes. |
Hi, I ran into the same issue. Needing to restart octant to check plugin changes during development etc. I put together this script to autobuild the plugin and restart octant on source changes: https://gist.github.com/jdolitsky/34b67113afe515e096064a4d01fd4dd6 |
Would it be useful to add some flag like |
Octant should be able to restart a plugin or plugins. Or perhaps you kill the plugin and Octant could could restart registered plugins. We will draft upma solution and tag the issue. |
Just heard of this script to help with plugin development, which looks promising: https://gist.github.com/jdolitsky/34b67113afe515e096064a4d01fd4dd6 I haven't tried it yet, but I plan to when I have time to play with plugin development again. |
My initial thought for doing something like this is to extend the existing process launcher to have a bit more management to it.
Related reading: |
I installed the sample plugin and it did not show up until I restarted.
The text was updated successfully, but these errors were encountered: