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

Update Developer's Guide: Installing and using poetry #768

Closed
pagrubel opened this issue Jan 16, 2024 · 10 comments
Closed

Update Developer's Guide: Installing and using poetry #768

pagrubel opened this issue Jan 16, 2024 · 10 comments
Assignees
Labels
documentation Required documentation good first issue Good for newcomers

Comments

@pagrubel
Copy link
Collaborator

pagrubel commented Jan 16, 2024

It looks like we just included all poetry commands available instead of what we need for actually running BEE.
We should limit that to only what we need. As it is right now it is confusing.

Define the next step once the poetry environment is up?
We may also want to suggest starting a branch if you are actually starting development.

@aquan9 aquan9 added the good first issue Good for newcomers label Jun 25, 2024
@aquan9
Copy link
Collaborator

aquan9 commented Jun 25, 2024

I defined this on paper for @AnnaLeah02 Maybe this might be a good first issue for her?

@Leahh02 Leahh02 self-assigned this Jun 25, 2024
@pagrubel pagrubel changed the title Update Developer's Guide Update Developer's Guide: Installing and using poetry Jun 27, 2024
@pagrubel
Copy link
Collaborator Author

Breaking this into two issues.

@pagrubel pagrubel added the documentation Required documentation label Jun 27, 2024
@Leahh02
Copy link
Collaborator

Leahh02 commented Jul 11, 2024

Need to include that in ~/.config/beeflow/bee.conf the neo4j_image should be changed to /projects/beedev/neo4j-5-17.tar.gz

@pagrubel
Copy link
Collaborator Author

Are you talking about in the documentation?

@Leahh02
Copy link
Collaborator

Leahh02 commented Jul 11, 2024

I am

@pagrubel
Copy link
Collaborator Author

That would be specific to LANL systems and the team so might not be appropriate

@Leahh02
Copy link
Collaborator

Leahh02 commented Jul 11, 2024

Oh ok, I won't add that to the documentation then

@pagrubel
Copy link
Collaborator Author

It would probably be advisable to put the version number without the specific location, also remember they can use the pull dependency options.

@Leahh02
Copy link
Collaborator

Leahh02 commented Jul 11, 2024

Gotcha, ok

@pagrubel
Copy link
Collaborator Author

Addressed in #899

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Required documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants