mitmproxy/dev

#!/bin/bash
set -e
VENV=../venv.mitmproxy

python -m virtualenv $VENV || { echo 'virtualenv is not installed. Exiting.' ; exit 1; }
source $VENV/bin/activate
pip install --src .. -r requirements.txt

echo ""
echo "* Created virtualenv environment in $VENV."
echo "* Installed all dependencies into the virtualenv."
echo "* Activated virtualenv environment."
merged with upstream changes in dev 2015-06-23 20:50:51 -05:00			`#!/bin/bash`
			`set -e`
Virtualenv is the one and only recommended dev environment - Create a "dev" script to create a virtualenv-based dev environment - Update the docs to remove non-virtualenv install recommendations - Update osx-binaries generation to use virtualenv TODO: - The dev script or an equivalent should be made to work on Windows - We still can't remove the annoying top-level command scripts, because pyinstaller doesn't support entry points. Once it does, they can go. 2015-03-12 22:12:15 +11:00			`VENV=../venv.mitmproxy`

merged with upstream changes in dev 2015-06-23 20:50:51 -05:00			`python -m virtualenv $VENV \|\| { echo 'virtualenv is not installed. Exiting.' ; exit 1; }`
Virtualenv is the one and only recommended dev environment - Create a "dev" script to create a virtualenv-based dev environment - Update the docs to remove non-virtualenv install recommendations - Update osx-binaries generation to use virtualenv TODO: - The dev script or an equivalent should be made to work on Windows - We still can't remove the annoying top-level command scripts, because pyinstaller doesn't support entry points. Once it does, they can go. 2015-03-12 22:12:15 +11:00			`source $VENV/bin/activate`
./dev: echo what we have done 2015-03-14 03:08:34 +01:00			`pip install --src .. -r requirements.txt`

			`echo ""`
			`echo "* Created virtualenv environment in $VENV."`
			`echo "* Installed all dependencies into the virtualenv."`
Add a check to see if virtualenv is installed. 2015-06-23 20:17:57 -05:00			`echo "* Activated virtualenv environment."`