update tutorial to launch and use private docker registry

I'll fix that!  ;)

> On Sep 19, 2014, at 5:42 PM, Ben Parees <notifications@github.com> wrote:
> 
> In examples/simple-ruby-app/README.md:
> 
> > @@ -62,23 +75,19 @@ All commands assume the `openshift` binary is in your path:
> >          ----------                             ----------          ----------
> >          20f54507-3dcd-11e4-984b-3c970e3bf0b7   complete            build-docker-20f54507-3dcd-11e4-984b-3c970e3bf0b7
> >  
> > -        
> > -8. Once the build is complete, push the resulting image to your Docker repository:
> > -
> > -        $ docker push <docker_username>/origin-ruby-sample        
> > -
> > -9. Modify the application template to reference your Docker image:
> > - * Change "image": "openshift/origin-ruby-sample", to "image": "&lt;docker_username&gt;/origin-ruby-sample",
> > - 
> > -10. Submit the application template for processing:
> > +     The build will be automatically pushed to the private docker registry running in OpenShift and tagged with the imageTag listed
> > +     in the buildcfg.json.  Note that the private docker registry is using ephemeral storage, so when it is stopped, the image will
> > +     be lost.  An external volume can be used for storage, but is beyond the scope of this tutorial.
> > +     
> > +9. Submit the application template for processing:
> "openshift kube apply" doesn't currently accept piped input that i can see.
> 
> Also it gives users a chance to see the generated env variable values (to compare w/ what the curl output gives them later).
> 
> —
> Reply to this email directly or view it on GitHub.