You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
When running docker locally, it's pretty silly that we have to do source ~/.virtualenv/rmc/bin/activate, considering it's an isolated
environment by design.
So either we should skip using the virtualenv in docker, or we
should change the docker environment to activate the virtualenv
automatically on boot somehow.
The text was updated successfully, but these errors were encountered:
When running docker locally, it's pretty silly that we have to do
source ~/.virtualenv/rmc/bin/activate
, considering it's an isolatedenvironment by design.
So either we should skip using the virtualenv in docker, or we
should change the docker environment to activate the virtualenv
automatically on boot somehow.
The text was updated successfully, but these errors were encountered: