anchor.diff:  them create PVCs and use the *fsGroup* setting for the Postgres containers to
   work using NFS.  There is most likely a smarter and more precise way to grant
   this permission but this is one suggested process.
  +
  +== Legal Notices
  +
  +Copyright © 2017 Crunchy Data Solutions, Inc.
  +
  +CRUNCHY DATA SOLUTIONS, INC. PROVIDES THIS GUIDE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
  +
  +Crunchy, Crunchy Data Solutions, Inc. and the Crunchy Hippo Logo are trademarks of Crunchy Data Solutions, Inc.
  
positive.code: 
  ==== OpenShift
  
  This OpenShift template will create a single master PostgreSQL instance.
  
  
  Running the example:
  
  ....
  cd $CCPROOT/examples/openshift/basic
  ./run.sh
  ....
  
  You can see what passwords were generated by running this command:
  
  ....
  oc describe pod basic | grep PG
  ....
  
  You can run the following command to test the database, entering
  the value of PG_PASSWORD from above for the password when prompted:
  
  ....
  psql -h basic.openshift.svc.cluster.local -U testuser userdb
  ....
  
negative.code: 
  This script will do the following:
  
   * Create a docker volume using the local driver for the master
   * Create a docker volume using the local driver for the replica
   * Create a container named *master* binding to port 12007
   * Create a container named *replica* binding to port 12008
   * Initialize the database using the predefined environment variables
   * Map the PostgreSQL port 5432 within the container to the localhost port 12000
  
  Start the containers by running the following.
  ....
  docker start master replica
  ....
  
  View the status of these containers by running:
  ....
  docker ps | grep 'master\|replica'
  ....
  
  This will display the container that was just created and started, and should state that it is up in addition to the IP address and port it resides on.
  
  If you need to diagnose the container, you can do so by viewing the logs.
  ....
  docker logs master
  docker logs replica
  ....
  
  The container creates a default database called *userdb*, a default user called *testuser* and a default password of *password*. Connect from your local host as follows:
  ....
  psql -h localhost -p 12007 -U testuser -W userdb
  psql -h localhost -p 12008 -U testuser -W userdb
  ....
  
  To shut down the instance, run the following:
  ....
  docker stop master replica
  ....
  