scripts/aws_install_dependencies.sh

#!/bin/bash

echo "Install dependencies"
cd /home/notify-app/notifications-admin;
pip3 install --find-links=vendor -r /home/notify-app/notifications-admin/requirements.txt
Added files to support AWS Code deploy 2015-11-30 15:44:16 +00:00			`#!/bin/bash`

Logging on dependencies 2015-12-02 10:15:46 +00:00			`echo "Install dependencies"`
Updated start scripts to not look up envrionemnt 2016-07-04 17:21:08 +01:00			`cd /home/notify-app/notifications-admin;`
Don't create wheels for dependencies but store offline: Previously we used AWS which meant that we could create wheels from our requirements and then install them offline which made deployments quicker. We're no longer using AWS so let's remove that. Although CloudFoundry supports installing dependencies in an offline environment as documented here: http://docs.cloudfoundry.org/buildpacks/python/#vendoring To achieve this we create a vendor/ directory which will contain the packages to install. This uses --no-index and --find-links so will not resolve for any dependencies from pypi. For this reason there is assumed confidence that the vendor/ directory will contain all of the dependencies we need. 2017-07-20 11:29:31 +01:00			`pip3 install --find-links=vendor -r /home/notify-app/notifications-admin/requirements.txt`