This repository contains Docker configuration files to start up a local installation of most of the parts of Mozilla's code-review-and-landing system, collectively known as "Conduit". This includes

• BMO, Mozilla's Bugzilla fork
• Phabricator, including extensions and patches
• Lando, both API and UI
• Transplant, the service that lands commits
• A Mercurial server
• A container ("local-dev") with various command-line tools including MozPhab

The suite allows only some services to be started up, if the whole system is not needed. It also provides the option of using both local clones and hosted images, so you need only have the code checked out for the service(s) you need to modify.

This suite can be used to demo Conduit services and to aid in development. This repository, however, should not be viewed as a substitute for self-contained tests in individual repositories.

1. You need to have docker and docker-compose installed.
2. For Lando, an Auth0 developer account. See the lando-ui README.md for instructions on how to set that up.
3. Also for Lando/Transplant, an AWS S3 bucket, which requires

• The bucket name
• AWS Access Key
• AWS Secret Key

• Pull the repository into a separate (e.g. conduit) directory.
• Go to the conduit/suite directory
• Depending on what services you plan to run, you may need to create a docker-compose.override.yml file. At the moment, this is only required for Lando and Transplant. If in doubt, please refer to the relevant projects. Here is a sample file:

version: '2'
services:
  lando-ui:
    environment:
      OIDC_DOMAIN: <your auth0 domain, e.g. account.auth0.com>
      OIDC_CLIENT_ID: <your auth0 client id for lando-ui>
      OIDC_CLIENT_SECRET: <your auth0 client secret for lando-ui>
      LANDO_API_OIDC_IDENTIFIER: <your auth0 api identifiier for lando-api>

  lando-api:
    environment:
      PATCH_BUCKET_NAME: <your aws patch bucket name>
      AWS_ACCESS_KEY: <your aws access key>
      AWS_SECRET_KEY: <your aws secret key>
      # Optional: 'http://lando-api.test' by default
      OIDC_IDENTIFIER: <your auth0 api identifiier for lando-api>
      OIDC_DOMAIN: <your auth0 domain>
      # Optional: 'inject_valid' by default
      LOCALDEV_MOCK_AUTH0_USER: <'default' | 'inject_valid' | 'inject_invalid'>

  autoland.transplant-init:
    environment: &transplant_secret
      LANDO_BUCKET: <your aws patch bucket name>
      LANDO_AWS_KEY: <your aws access key>
      LANDO_AWS_SECRET: <your aws secret key>

  autoland.transplant-api:
    environment: *transplant_secret

  autoland.transplant-daemon:
    environment: *transplant_secret

• Run docker-compose build

If you are running Lando, you will need to first initialize the database:

$ docker-compose up -d lando-api
$ docker-compose exec lando-api lando-cli init
$ docker-compose down

The "local-dev" container includes command-line tools used to interact with Conduit services.

To set up the container,

1. $ docker-compose run local-dev. A shell will open.
2. $ ./clone_repositories.sh. Repositories will be cloned from http://hg.test/
3. The Mercurial repository is placed in the ./test-repo/.
4. Run moz-phab install-certificate to authenticate yourself in the local-dev environment. Choose one of the Preconfigured Users (preferably the conduit one)
5. Use as a normal local development repository.

Note: A git-cinnabar version of the same repository is located at ./test-repo-cinnabar/. The forked version of Arcanist is also provided and aliased as the cinnabarc.

Note: To run moz-phab under Python3 start the prepared environment:

$ source $VIRTUAL_ENV3/bin/activate

You can either configure an existing Firefox instance to use our proxy, or run a preconfigured Firefox.

To configure your current browser:

1. Open Options -> Network Proxy -> Settings
2. Choose the Manual Proxy Configuration radio button
3. Set HTTP Proxy to localhost and Port to 1080.

To run Firefox with an empty profile:

1. Please set the environment variable FIREFOX_CMD to /path/to/firefox if your system does not recognize the firefox command.
2. In a new terminal, run firefox-proxy, or firefox-proxy $(docker-machine ip) if you are using docker-machine.
3. A new browser with an empty profile will open.

• Phabricator - http://phabricator.test
• Lando - http://lando-ui.test
• Lando API - http://lando-api.test/ui via Swagger UI.
• Bugzilla - http://bmo.test
• Mercurial - http://hg.test

Each Conduit application also has its own corresponding Docker Compose configuration file.

This is useful for doing development work as, it allows you to specify which application should run from a local clone instead of from a hosted image.

To allow the override compose files to work properly, you need to have your repository directory structure set up correctly. Please clone the repositories you wish to use locally to the conduit directory.

$ git clone [email protected]:mozilla-conduit/arcanist.git
$ git clone [email protected]:mozilla-conduit/autoland-transplant.git
$ git clone [email protected]:mozilla-bteam/bmo.git
$ git clone [email protected]:mozilla-conduit/lando-api.git
$ git clone [email protected]:mozilla-conduit/lando-ui.git
$ git clone [email protected]:mozilla-services/phabricator-extensions.git
$ git clone [email protected]:mozilla-conduit/review.git

The phabricator-extensions build process requires existence of a phabext.json file. Add it with the command:

$ echo "{}" > phabricator-extensions/phabext.json

If you've installed all of the above projects, your directory structure would look as below:

conduit
├── arcanist/
├── autoland-transplant/
├── bmo/
├── suite/
├── lando-api/
├── lando-ui/
├── phabricator-extensions/
└── review/

You can use each app from its local repository. For example, to run the phabricator-extensions code from a local repository instead of the mozilla/phabext image,

# Build the containers
$ docker-compose -f docker-compose.yml -f docker-compose.phabricator.yml -f docker-compose.override.yml build
# Start the containers
$ docker-compose -f docker-compose.yml -f docker-compose.phabricator.yml -f docker-compose.override.yml up -d

You can also use multiple apps from local repositories. For example, to work on both Phabricator and Bugzilla,

$ docker-compose -f docker-compose.yml -f docker-compose.phabricator.yml -f docker-compose.bmo.yml -f docker-compose.override.yml up --build -d

And for example to work on lando-ui and lando-api,

$ docker-compose -f docker-compose.yml -f docker-compose.lando-api.yml -f docker-compose.lando-ui.yml -f docker-compose.override.yml up --build -d

Note that normally you must have -f docker-compose.yml as the first option and -f docker-compose.override.yml as the last one.

To work on a local version of the Arcanist fork, load the docker-compose.cinnabarc.yml configuration. This will modify the arc command in the local-dev service. Similarly, to load a local version of the ARC wrapper "review" , load the docker-compose.review.yml.

If you don't want to spin up all configured containers, you can specify the ones you'd like to work on. The command below runs phabricator.test, phabricator, phabdb, lando-api.test, lando-api and lando-api.db to allow the verification of the integration between Phabricator and Lando API:

docker-compose up phabricator.test lando-api.test

For performing administration tasks in Phabricator, first log out of Phabricator and then go to http://phabricator.test/auth/start/?admin and log in with

user:admin, password:password123456789!

To log in as a normal test user, you will need to use BMO for auth delegation. Log out of Phabricator and then click on 'Log In or Register'. You will be redirected to BMO's login page.

user:[email protected], password:password123456789!

We also have a ConduitReviewer account that can be opened in a second private browser window for performing the other half of the review dance. On the BMO login page enter:

user:[email protected], password:password123456789!

After login, if it complains that you do not have MFA enabled on your BMO account, click on the 'Preferences' link that will allow you to configure TOTP and then you should be able to login to Phabricator.

For performing administrative tasks on BMO, you will need to log out of BMO and then log in at http://bmo.test/login with the following credentials:

user:[email protected], password:Te6Oovohch

As noted in this Phabricator ticket, the only way we can set up an out-of-the-box Phabricator is to preload the application database with the settings we want.

To update the preloaded database with new settings:

1. Important: Run docker-compose down and docker volume rm suite_phabricator-mysql-db to ensure you have a fresh DB!
2. Start the application with docker-compose up and log in with the appropriate user ("admin" to update global settings, "phab-bot" for things like API keys).
3. Change the desired setting.
4. Run docker-compose run phabricator dump > demo.sql to dump the database.
5. Edit demo.sql and delete the extra shell output at the beginning and at the end of the file.
6. $ gzip demo.sql
7. $ mv demo.sql.gz docker/phabricator/demo.sql.gz
8. Submit a PR with the changes.

The local-dev service uses repositories cloned from http://hg.test/. You will need to re-clone them every time Mercurial server images are created. There is a bash script which will remove the existing directories and clone the repositories using hg and git-cinnabar:

# ./clone_repositories.sh

Start the suite:

$ docker-compose up -d
$ docker-compose exec lando-api lando-cli init

Create a diff:

$ docker-compose run local-dev
# ./clone-repositories.sh
# cd test-repo
# echo test >> README
# hg commit -m "test info added"
# moz-phab install-certificate
# moz-phab submit -b 1

Log in to http://lando-ui.test.

Navigate to http://lando-ui.test/revisions/D2.

Confirm the warning and click on the Land button.

Reload the page. Observe the landing confirmation.

Check if the commit is present in the http://hg.test/.