-
Notifications
You must be signed in to change notification settings - Fork 3
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
Clean up <bee_workdir> #734
Comments
Data base files are in the top level reconsider. Determine the rules and publish in contributing area. |
This has been cleaned up some, here is listing of the current directories in bee_workdir (by default ~/.beeflow): These are the current directories: dependent containers (neo4j & redis) are unpacked into deps now that they are named _container we could put their associated directories in there Should we just leave well enough alone? Maybe just have a README that describes the top level files and have some future suggested changes such as a directory for all the database files (tm.db, sched.db, wfm.db), move redis/redis.sock with the other sockets, move redis and celery into deps, call archives archived_workflows and workflows, active-workflows Or I could start working on the changes. even break it into small PR's The top level would then look like this: active_workflows (was workflows) |
I think that's a great suggestion! The current version definitely needs some refining. |
Ok I made a list at the top of this issue and plan to start on it. If anyone picks part of it up let me know. I'll start with the first item. |
To make this light work that we can pick up here and there check off the tasks and include a PR# by the task as they are completed. Tasks for organizing the bee_workdir:
We started with sockets all in one directory, now there are sockets for redis in another directory. Also, we had the idea of having one dependent container in <bee_workdir>/deps.
We need to clean up <bee_workdir> and make some rules for it.
The text was updated successfully, but these errors were encountered: