anchor.diff:  be used to login to the local cluster. The recommended user name and password combination is
   developer/developer, because it already has a default project _myproject_ and also can
   https://docs.openshift.org/latest/architecture/additional_concepts/authentication.html#authentication-impersonation[impersonate]
  -the administrator user. This allows to run administrator commands using the `--as system:admin` parameter.
  +the administrator. This allows you to run administrator commands using the `--as system:admin` parameter.
   
   To login as administrator, use the system account:
   
  
positive.code: you need to modify the above command depending on your Operating System,
  your shell environment and its interpolation behavior.
  
  For example, if you use PowerShell on Windows 10 modify the above command to:
  ....
  $  .\minishift.exe --% openshift config set --patch "{\"routingConfig\": {\"subdomain\": \"192.168.99.101.nip.io\"}}"
  ....
  
  If you use Command Prompt you may need to use:
  ....
  minishift.exe openshift config set --patch "{\"routingConfig\": {\"subdomain\": \"192.168.99.101.nip.io\"}}"
  ....
  ====
  
  [[example-change-openshift-routing-suffix]]
  
negative.code: The `minishift start` command creates an OpenShift instance using the
  https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md[cluster up] approach.
  
  For this purpose it copies the `oc` binary onto your host. It is located in the  _~/.minishift/cache/oc/{openshift-version}_ directory, provided you use Minishift's default version of OpenShift.
  You can add this binary to your `PATH` using link:../command-ref/minishift_oc-env{outfilesuffix}[`minishift oc-env`] which displays the command you need to type into your shell.
  The output of `oc-env` differs depending on the operating system and the shell type.
  
  ----
  $ minishift oc-env
  