treeherder/requirements.txt

# Our pip requirements files are kept under `requirements/`, however Heroku's
# Python buildpack only looks for `<repo_root>/requirements.txt`, so we use
# pip's include syntax to load the production dependencies file from here.

-r requirements/common.txt
Bug 1165259 - Add infrastructure documentation (#4766) - Adds a new "infrastructure" section to the docs, which describes architecture, administration and troubleshooting (fixes bug 1165259). - Adds code comments to any deployment-related files in the repository. - Adds documentation for the various ways in which users can access Treeherder data (fixes bug 1335172). - Reorganises the structure of some of the existing non-infrastructure docs, to make the documentation easier to navigate. 2019-03-12 00:39:34 +03:00			# Our pip requirements files are kept under `requirements/`, however Heroku's
			# Python buildpack only looks for `<repo_root>/requirements.txt`, so we use
			`# pip's include syntax to load the production dependencies file from here.`
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
			`-r requirements/common.txt`