anchor.diff:  ----
   
   This removes the previous *emptyDir* volume for the deployment config and adds a
  -claim for 1 gigabyte of persistent storage mounted at `/sonatype-work`, which
  -is where our dependencies will be stored. Due to the change in configuration,
  +claim for one gigabyte of persistent storage mounted at `/sonatype-work`, which
  +is where the dependencies will be stored. Due to the change in configuration,
   the Nexus pod will be redeployed automatically.
   
  -Verify that Nexus is running by refreshing the Nexus page in your browser. You
  -can monitor the deployment's progress using:
  +To verify that Nexus is running, refresh the Nexus page in your browser. You can
  +monitor the deployment's progress using:
   
   ----
   $ oc get pods -w
  
positive.code: link:https://books.sonatype.com/nexus-book/reference/config.html[the Nexus documentation]
  to configure your build properly.
  
  Furthermore, make sure that you give each pod enough resources to
  function. You may have to edit the pod template in the Nexus deployment
  configuration to request more resources.
  xref:../deployment#creating-a-deployment-configuration[Learn more about setting deployment resources in pod templates].
  
  [[nexus-setting-up-nexus]]
  == Setting up Nexus
  
  Use `new-app` to download and deploy the official Nexus container image.
  
  ----
  oc new-app sonatype/nexus
  ----
  
  Create a route by exposing the newly created Nexus service:
  
  ----
  oc expose svc/nexus
  ----
  
  Use *oc get routes* to find the pod's new external address.
  
  ----
  oc get routes
  ----
  
  The output should resemble:
  
  ----
  NAME      HOST/PORT                              PATH      SERVICES   PORT       TERMINATION
  nexus     nexus-myproject.192.168.1.173.xip.io             nexus      8081-tcp
  ----
  
  Confirm that Nexus is running by navigating your browser to the URL under
  *HOST/PORT*. To sign in to Nexus, the default administrator username is *admin*,
  and the password is *admin123*.
  
  Nexus comes pre-configured for the Central Repository, but you may need others
  for your application.  For many Red Hat images, it is recommended to add the
  *jboss-ga* repository at *_https://maven.repository.redhat.com/ga/_*.
  link:https://books.sonatype.com/nexus-book/reference/config-maven.html[Learn how to add repositories].
  
  [[nexus-using-probes-to-check-for-success]]
  === Using Probes to Check for Success
  
  This is a good time to set up readiness and liveness probes. These will
  periodically check to see that Nexus is running properly.
  xref:../application_health.adoc#dev-guide-application-health[Learn more about probes].
  
  ----
  $ oc set probe dc/nexus \
  
negative.code: $ oc logs build/jee-ex-1 --follow
  ----
  
  Replace `<Nexus_Project>` with the project name of the Nexus repository. If it
  is in the same project as the application that is using it, you can remove the
  `<Nexus_Project>.`.
  xref:../../architecture/additional_concepts/networking.adoc#architecture-additional-concepts-networking[Learn more about DNS resolution in {product-title}].
  