Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BEE-Dependencies-NoContainers #907

Open
aquan9 opened this issue Aug 27, 2024 · 0 comments
Open

BEE-Dependencies-NoContainers #907

aquan9 opened this issue Aug 27, 2024 · 0 comments
Assignees

Comments

@aquan9
Copy link
Collaborator

aquan9 commented Aug 27, 2024

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.

@pagrubel pagrubel changed the title BEE-NoContainers BEE-Dependencies-NoContainers Sep 10, 2024
@aquan9 aquan9 self-assigned this Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant