Multiple isolated devstacks on the same host

[Zachary_Trabookis]

Additional notes when changing release can be found here.

edxenv bash alias to switch between releases.

Docker Devstack – Multiple Releases – One Machine

@arbrandes Thanks for testing this PR out. Glad it worked for you. I also wanted to note that I’m keeping my major named releases in separate directories to avoid messing something up. /Dev/EducateWorkforce/Repos/open-edx/devstack.master /Dev/EducateWorkforce/Repos/open-edx/devstack.ironwood /Dev/EducateWorkforce/Repos/open-edx/devstack.hawthorn I’m using this .bash_profile alias to switch between the releases setting the appropriate virtual environment and setting me to start in the devst…

direnv to handle environmental changes.

Docker Devstack – Multiple Releases – One Machine

Neat! What I and some folks at Opencraft have been doing is similar, but sorta the other way around. We use direnv so that when we’re in a particular directory, a set of variables is loaded, venvs activated, etc. The point is that this will now be even more useful with your patch! For example, this is my .envrc: # ~/src/devstack-juniper/.envrc export COMPOSE_PROJECT_NAME=devstack-juniper export OPENEDX_RELEASE=devstack-juniper export VIRTUAL_ENV=venv layout python-venv (I set OPENEDX_RELE…