Example init output

gistfile1.txt

$ oc init
On branch init @ 3082f62 with remote [email protected]:openshift/origin.git

When initializing a repository, you can choose how you want to develop:

1. Build from your local code using a binary build (--binary)

   This is the simplest setup. Your local code will be uploaded on each build, but you won't
   be able to rebuild without uploading your code again. Best used when you're testing out a
   build locally.

2. Build from the remote Git repository and trigger builds with webhooks (--webhooks)

   This setup works best if you are already collaborating with others on GitHub or a hosted
   Git repository and want to build when code is merged to a branch. You'll have to configure
   your remote repository to send a webhook notification to your OpenShift server.

3. Set up a Git server on OpenShift and push code directly to that repository (--git)

   This allows you to collaborate with others when you don't have or want a hosted Git repository.
   Each time you git push, your code will be built and deployed. A new 'openshift' remote will be
   created in the local Git repository for you to push to.

4. Use hot-deployment to rapidly iterate on your code (--hot-deploy)

   For dynamic languages like JavaScript or Ruby, or compiled languages like Java where your IDE
   compiles .class files, you can mirror your local directory to the running instance in OpenShift
   and have changes be reflected instantly. Only works if the base image is properly configured,
   and you may need to specify additional environment variables to enable code reload.

Run this command again with one of the flags defined above.

@bparees would you understand this if you saw it?