You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Internally we want to be able to run BEE completely without containers, in case container usage is shutdown internally.
This requirement comes down from our leadership.
To that end, we want to be able to run using instances of Neo4j and Redis that are available through Spack.
This will involve adding an option to the config to use Spack versions of the dependencies rather than the containerized versions, or detecting whether Beeflow was installed using Spack/pip/poetry.
This will involve changing the way we start up the neo4j and Redis instances after a beeflow core start
It may also involve changing the interfaces to those components to support bare metal.
The text was updated successfully, but these errors were encountered:
Internally we want to be able to run BEE completely without containers, in case container usage is shutdown internally.
This requirement comes down from our leadership.
To that end, we want to be able to run using instances of Neo4j and Redis that are available through Spack.
This will involve adding an option to the config to use Spack versions of the dependencies rather than the containerized versions, or detecting whether Beeflow was installed using Spack/pip/poetry.
This will involve changing the way we start up the neo4j and Redis instances after a
beeflow core start
It may also involve changing the interfaces to those components to support bare metal.
The text was updated successfully, but these errors were encountered: