* Adding missing repo name. Small tidy ups

* Fixed typos and broken link

…provisioners (#1204)

* Enable Console do be deployed in K8s clusters without shared storage provisioners

* Update Readme

- We use a multi-buildpack to build the console
- The cf multi-buildpack does not support system buildpacks, in the scf
world these would be compatible with scf's opensuse42 stack
- So we specify the use of standard cf buildpaForce the console cf app to use the cflinuxfs2 stack
- We use a multi-buildpack to build the console
- The cf multi-buildpack does not support system buildpacks, in the scf
world these would be compatible with scf's opensuse42 stack
- So we specify the use of standard cf buildpacks, which are incompatible
with opensuse42, so need to force the use of cflinuxfs2
- We've also tried setting the scf buildpacks in the multo-buildpack however
get an error. We should look into this and once resolved apply that change and
revert this PR. Alternatively get the multi-buildpack to support system
buildpacks.cks, which are incompatible with opensuse42, so need to force
the use of cflinuxfs2.

At least with Kubernetes 1.6 a hostPath volume mount will be owned
by root and have 750 permissions.

The docker-entrypoint.sh script will try to assign ownership to the
postgres user:

	mkdir -p "$PGDATA"
	chmod 700 "$PGDATA"
	chown -R postgres "$PGDATA"

But this is insufficient if PGDATA points to a subdirectory of the
mount directory since the postgres user doesn't have "execute"
permission and therefore cannot reach the data directory.