Split requirements.txt to separate files for clients/development/docs/agents #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This splits out the requirements file so users can install a minimal amount of packages just required for running ocs clients, while optionally being able to install all packages needed for development, etc.
I've updated the documentation to describe the separate requirements files. We default to clients and docs dependencies. Individual agents are now managing their own dependencies, so those will be installed only in the specific Agent containers. Lastly there's the dev.txt file, which includes pytest. We use that in the Dockerfile for building ocs images since we run the tests in the CI pipeline. This could be split out if desired, but I'm not sure it's worth doing.
Other notes:
Motivation and Context
Closes #92
How Has This Been Tested?
I'm working on testing this. Tests pass so far though.
Types of changes
Checklist:
develop
branch.