Allow Multiple requirements.txt files per compute
Problem
Currently each compute instance can only be associated with one requirements.txt file. This limits flexibility for users working across multiple projects that require different dependencies. Switching between projects / tasks still requires manual editing of requirements.txt and file replacement (uninstall / install).
Proposed resolution
- Allow multiple
requirements.txtfiles to be registered per compute, with an option to select one when starting or switching projects. - Optionally support project-level dependency files for automatic environment setup.
Benefits
- Flexibility: Easily manage and switch between dependencies for different projects.
- Efficiency: Reduce manual configuration time and errors.
- Scalability: Simplify collaboration across teams with diverse workloads.
Comments
-
greetings team oracle !
may we say !
if interoperability between different platforms is suggested then how to mitigate real time cyber snooping from different data packet analyzers …
thanks for listening!
thanks for time!
happy to learn
0 -
You can have different names for requirements files today and install many different requirements files into compute.
1 -
Thanks for the update @David Allan-Oracle - would you recommend to name requirements files based on a project, and then installing whichever requirements file you are working on into a compute for ease of use?
0
