normandy/compose
Rehan Dalal 21c2f7ff75 Update docs / CI 2017-01-24 17:08:41 -05:00
..
bin Merging compose to master 2017-01-05 09:53:17 -08:00
etc Merging compose to master 2017-01-05 09:53:17 -08:00
.gitignore Merging compose to master 2017-01-05 09:53:17 -08:00
README.md Update docs / CI 2017-01-24 17:08:41 -05:00
docker-compose.yml Fix #392: Add mock-recipe-server project. 2017-01-11 13:35:22 -08:00
normandy-base.yml Fix #392: Add mock-recipe-server project. 2017-01-11 13:35:22 -08:00

README.md

This project holds all the bits to get a prod-like Normandy running using Docker Compose.

  1. Install Docker and Docker Compose, and start the Docker daemon (possibly via Docker Machine).
  2. Clone this repo, and cd into it.
  3. ./bin/genkeys.sh to create keys for HTTPS.
  4. docker-compose up -d to download Docker images, and run them in the background.
  5. docker-compose run normandy ./manage.py migrate to create the needed database tables.
  6. docker-compose run normandy ./manage.py createsuperuser to create a user you can log in with.
  7. docker-compose run normandy ./manage.py update_actions to load the action code into the database.
  8. docker-compose run normandy ./manage.py update_product_details to update the Mozilla product details.
  9. docker-compose run normandy ./manage.py initial_data to load the initial channel and country data.
  10. Open http://localhost:8000 or http://$(docker-machine ip):8000 in your browser. Accept the self-signed certificate.
  11. Later, run docker-compose stop to shut everything down.

Signing

This compose configuration is set up to use [Autograph][] to sign recipes. These signatures are required for [the system addon][]. They are signed using a development key, which is publically known and shouldn't be trusted for anything serious. To instruct Firefox to trust this development key, set the pref security.content.signature.root_hash to 4C:35:B1:C3:E3:12:D9:55:E7:78:ED:D0:A7:E7:8A:38:83:04:EF:01:BF:FA:03:29:B2:46:9F:3C:C5:EC:36:04.