Install datalab as editable inside docker build to make env passing simpler #917
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.
In #914 we switched to a non-editable install inside the docker containers, which means that datalab runs from the installed module (
/opt/.venv/lib/python3.10/site-packages/...
etc), but the dotenv loader only looks in that folder and above (rather than the datalab source folder).Long term,
but short-term, we can just got back to an editable install (makes no difference inside the container) so that the current deployment
.env
path is still found.