Plugin Dependency Management

[kepoling]

Currently, the way dependencies are managed, if a plugin adds a new dependency that dependency has to be added to the core forge engine. This obviously isn't scalable and goes against the pattern we have tried to put in place. Upon installing a plugin, that plugin should install all of its own dependencies.

[tucamsam]

We should be able to set up separate virtual environments for each plugin to allow each to have its own sandbox. I'll start on this approach and see how far we can take it.

[offbrand]

How would that work with the plugins themselves being able executed as raw code called from the primary app?

…

Sent from my iPhone

On Apr 29, 2020, at 9:43 AM, Cameron ***@***.***> wrote:  We should be able to set up separate virtual environments for each plugin to allow each to have its own sandbox. I'll start on this approach and see how far we can take it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[tucamsam]

Still thinking my way through it - obviously the other option is to force all plugins into the same virtual environment, but as we add more and more plugins, I fear that will be tough to maintain.