Closed Bug 1165259 Opened 10 years ago Closed 6 years ago

Document Heroku & supporting infrastructure in read the docs

Categories

(Tree Management :: Treeherder, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(2 files)

Not urgent. Not sure where best to put these, since it's kind of infra-specific and only applies to people who have Heroku access - but would still be good to document this somewhere. I think maybe Read the docs might be a good place? (And then we can slowly deprecate https://mana.mozilla.org/wiki/display/websites/treeherder.mozilla.org) Things to cover: * Installing the heroku toolbelt * Authenticating * Adding a heroku remote to an existing repo clone (eg https://devcenter.heroku.com/articles/git#creating-a-heroku-remote) * Some links to useful commands
No longer blocks: treeherder-heroku-prototype
Also: * How to connect to the Heroku RDS instance. ie: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToInstance.html (remembering to use the CA cert mentioned there; if using MySQL Workbench "Use SSL" should be set to "require" and the field to enter the path to the cert is called "SSL CA file") ...and using the host/user/password contained in the heroku env DATABASE_URL - eg: [~/src/treeherder]$ heroku config | grep DATABASE_URL DATABASE_URL: mysql://th_admin:REDACTED@treeherder-heroku.REDACTED.us-east-1.rds.amazonaws.com/treeherder DATABASE_URL_RO: mysql://th_admin:REDACTED@treeherder-heroku.REDACTED.us-east-1.rds.amazonaws.com/treeherder
(In reply to Ed Morley [:emorley] from comment #1) > and the field to enter the path to the > cert is called "SSL CA file") You can also use the CA file from the treeherder repo: deployment/aws/combined-ca-bundle.pem
Eugh sorry multi-post. Instead of: > [~/src/treeherder]$ heroku config | grep DATABASE_URL You can also just look at the web UI: https://dashboard.heroku.com/apps/treeherder-heroku/settings -> "Reveal Config Vars"
It's worth noting that on the Neroku dynos, the mysql command line client isn't available, so |./manage.py dbshell| won't work. So either connect remotely using mysqlworkbench or a mysql cli tool on your local machine, or else use |./manage.py run_sql ...| (for things that need to run against multiple project DBs).
Looking at the FAQ page, it looks like the required mysql CLI command (if using that instead of mysqlworkbench) is (run from the treeherder src repo): [~/src/treeherder] mysql -u th_admin -h treeherder-heroku.REDACTED.us-east-1.rds.amazonaws.com --ssl-ca=deployment/aws/combined-ca-bundle.pem --ssl-verify-server-cert And then enter the password when prompted.
It's also perhaps worth mentioning people can follow Heroku infra changes here: https://devcenter.heroku.com/changelog or via feed: https://devcenter.heroku.com/changelog
(In reply to Ed Morley [:emorley] from comment #6) > It's also perhaps worth mentioning people can follow Heroku infra changes > here: And subscribe to infra issues here: https://status.heroku.com/
Assignee: nobody → emorley
Priority: P3 → P2
Summary: Add Heroku setup steps to the docs → Document Heroku & supporting infrastructure in read the docs
Attachment #8796985 - Flags: review?(klibby) → checkin+
Status: NEW → ASSIGNED
Priority: P2 → P1
Depends on: 1530206
Component: Treeherder: Docs & Development → TreeHerder
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: