treeherder/requirements.txt

# HEROKU REQUIREMENTS

-r requirements/common.txt

django-heroku-memcacheify==1.0.0 --hash=sha256:971c63f9af5bee2884bbfd308457b6675b35b89a33cf42c1c4f0a554c324a563
Bug 1145606 - Setup treeherder to deploy on heroku I added a Procfile listing all the different python services treeherder needs. Heroku provides deployment-specific settings via environment variables, so I had to modify the settings file to listen to them where that wasn't the case. I created an enviroment variable IS_HEROKU which allows to have a heroku-only configuration where needed. The db service is provided by Amazon RDS, which requires a ssl connection. To enable ssl in the MySQLdb python client I had to modify Datasource (and bump up the version used). The cache service is provided by the memcachier heroku addon. Heroku recommends to use pylibmc, so I set it up according to the docs here https://devcenter.heroku.com/articles/memcachier#python. The amqp service is provided by the CloudAMQP addon. I added a post_compile script that runs every time we deploy. We should run every build step we require in there, like static asset minification, collection, etc. To share the oauth credentials among the various services I used an environment variable. I also added an option to export_project_credentials so that the credentials can be printed to stdout. This should come handy when we will need to update the environment-stored credentials with the ones in the db. 2015-05-01 13:01:11 +03:00			`# HEROKU REQUIREMENTS`

			`-r requirements/common.txt`

Bug 1213230 - Use pip 8's require-hashes feature instead of peep As of pip 8, peep has now been integrated into pip. Migrating from peep to this native feature has several advantages: * It avoids the complexity/learning curve of using a wrapper around pip. * It means we do not need to fork the official Heroku Python buildpack (which handles pip installation of requirements files) in order to use hash verification on Heroku. (Once the buildpack updates to pip 8.) * Omitted sub-dependencies result in install-time errors rather than the user discovering omissions at run-time. * pip's native caching is used, and all packages are installed in one pip invocation, so it's significantly faster. * It has better handling of errors and corner cases. Key facts about the native feature: * hash-checking mode is enabled if at least one hash is found in the requirements files passed to pip, or can be force enabled by passing `--requires-hashes` when running `pip install`. * Once enabled, hash-checking mode enforces that all packages: - are pinned to a specific version - have hashes listed - have all sub-dependencies specified * Older versions of pip will error out if either `--require-hashes` or the requirements file `--hash` syntax is used, meaning it's not possible to accidentally lose hash-checking protection if the pip used is older than expected. For more details, see: https://pip.pypa.io/en/stable/user_guide/#hash-checking-mode https://pip.pypa.io/en/stable/reference/pip_install/#hash-checking-mode The pip version on Travis and in the Vagrant virtualenv has been updated to 8.0.2 in bug 1241144, and the stage/prod virtualenv in bug 1241519. The Heroku Python buildpack pip was updated in bug 1241909. The requirements files hashes were ported using `peep port`, and then comments/URLs re-added by hand. 2016-01-20 19:22:54 +03:00			`django-heroku-memcacheify==1.0.0 --hash=sha256:971c63f9af5bee2884bbfd308457b6675b35b89a33cf42c1c4f0a554c324a563`