On AWS Elastic Beanstalk, I have some Python packages installed in a directory that is not part of the standard Python packages path (either for 2.6.x or for the 2.7.x version used by the Elastic Beanstalk environment). As a result, these packages are not (by default) visible to the AWS-EB deployment processes when it installs packages listed in requirements.txt, which can result in redundant packages being installed, often at the cost of (very) long deployment times.
Is there a way to make the directory where my packages are installed visible to the deployment process?
Aucun commentaire:
Enregistrer un commentaire