Clarify gcr.io replacement instructions
@@ -34,6 +34,16 @@ gcloud compute zones list
Currently, each component reads a local config file `matchmaker_config.json` , and all components assume they have the same configuration. To this end, there is a single centralized config file located in the `<REPO_ROOT>/config/` which is symlinked to each component's subdirectory for convenience when building locally.
+**NOTE** 'defaultImages' container images names in the config file will need to be updated with **your container registry URI**. Here's an example command in Linux to do this (just replace YOUR_REGISTRY_URI with the appropriate location in your environment, should be run from the config directory):
+```
+sed -i 's|gcr.io/matchmaker-dev-201405|YOUR_REGISTRY_URI|g' matchamker_config.json
+```
+For MacOS the `-i` flag creates backup files when changing the original file in place. You can use the following command, and then delete the `*.backup` files afterwards if you don't need them anymore:
+```
+sed -i'.backup' -e 's|gcr.io/matchmaker-dev-201405|YOUR_REGISTRY_URI|g' matchamker_config.json
+```
+If you are using the gcr.io registry on GCP, the default URI is `gcr.io/<PROJECT_NAME>`.
+
We plan to replace this with a Kubernetes-managed config with dynamic reloading when development time allows. Pull requests are welcome!
## Running Open Match in a development environment
