Detail workflow for plugins that are not open source

[backstage]

Detail workflow for plugins that are not open source

[nikek]

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.

[stefanalund]

[Rugvip]

Should document this as a part of #287. The scaffolded app should be able to create it's own plugins.

[adamdmharvey]

Some of this now exists in the https://backstage.io/docs/plugins/ .

But I think specifically closure of this issue involves authoring the page here:

https://backstage.io/docs/plugins/publish-private

Still open for contributors, esp those who may be doing this already.

[andrewthauer]

Curious if this publish private page is intended to document just plugins that are published to a private repo and/or for custom plugins within an orgs backstage instances monorepo?

[freben]

Both, right? I think the dev experience should be fairly similar.

[andrewthauer]

Partially the same I would think. However, separate repos requires more setup and are more work to test from my experience. I don't think there is much of a difference between publishing open source vs private in the separate repo case. So probably makes sense to cover all scenarios and rename the docs page accordingly.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Parsifal-M]

Hey Team! (@freben )

Is anything pending on this? I am sorting the good first issue backlog on age to see if I can help cleanup 😄

Its not 100% clear to me whats still pending on this... Please let me know if I can help out?

Thanks!

[Rugvip]

@Parsifal-M thank you for doing that! 😁

To be honest this one doesn't seem vary actionable at this point, so going to close it. Glad if you want to have a look at a different one though!