-
Hey guys, I'm looking for best practices for plugin development. Currently, the only thing that comes to my mind, is just to fork the whole roadrunner repo and add changes in a separate branch. I tried to implement my own "main" package with rr command, but everything exists in internal directory and I cannot import it into my package. Also, I cannot alter container.Plugins() function without changing the file directly. Can you suggest how to do it in the right way? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
Hey @fr05t1k. You don't need to fork any repository to add your custom plugin. A few days ago we introduced a new tool called velox.
type Plugin struct {}
you_super_plugin = { ref = "master", owner = "you", repository = "super_plugin" }
Next week I'll create a video tutorial about plugin development. It'll be on our YT channel: https://www.youtube.com/channel/UCHT6-FZGh5Y7JUGJyB8_M0Q/videos |
Beta Was this translation helpful? Give feedback.
Hey @fr05t1k. You don't need to fork any repository to add your custom plugin. A few days ago we introduced a new tool called velox.
So, to create your own plugin (only GitHub (private repos too) supported at the moment), you need to do the following:
vx b…