Backstage: Detail workflow for plugins that are not open source
So I create a plugin and it gets added to the main app. What if this plugin should not be open sourced? How do we I move it to an internal repo and stil use it in the main Backstage app?
This needs to be documented, and ideally supported in the CLI.
stefanalund
All 3 comments
I think it's more about documenting how to set up a private main app that depends on the open sourced core. Any plugins created within your main app shouldn't be open either, unless you decide specifically to ship those plugins to npm.
nikek
on 5 Mar 2020
👍2
stefanalund
on 6 Mar 2020
Should document this as a part of #287. The scaffolded app should be able to create it's own plugins.
Rugvip
on 17 Mar 2020
Was this page helpful?
0 / 5 - 0 ratings
Related issues
Fox32
路
3Comments
ruarfff
路
5Comments
emmaindal
路
3Comments
emmaindal
路
3Comments
fastfrwrd
路
4Comments
Most helpful comment
I think it's more about documenting how to set up a private main app that depends on the open sourced core. Any plugins created within your main app shouldn't be open either, unless you decide specifically to ship those plugins to npm.