Skip to content

Commit e3b7852

Browse files
committed
Rename osc -> oc
1 parent aa4fad5 commit e3b7852

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,35 +11,35 @@ One possible option is to use the Docker all-in-one launch as described in the [
1111

1212
If you don't have a project setup all ready, go ahead and take care of that
1313

14-
$ osc new-project nodejs-echo --display-name="nodejs" --description="Sample Node.js app"
14+
$ oc new-project nodejs-echo --display-name="nodejs" --description="Sample Node.js app"
1515

1616
That's it, project has been created. Though it would probably be good to set your current project to this (thought new-project does it automatically as well), such as:
1717

18-
$ osc project nodejs
18+
$ oc project nodejs
1919

2020
### The app ###
2121

2222
Now let's pull in the app source code from [GitHub repo](https://github.com/openshift/nodejs-ex) (fork if you like)
2323

2424
#### create ####
2525

26-
$ osc new-app https://github.com/openshift/nodejs-ex
26+
$ oc new-app https://github.com/openshift/nodejs-ex
2727
2828
That should be it, `new-app` will take care of creating the right build configuration, deployment configuration and service definition. Next you'll be able to kick off the build.
2929

3030
Note, you can follow along with the web console (located at https://ip-address:8443/console) to see what new resources have been created and watch the progress of the build and deployment.
3131

3232
#### build ####
3333

34-
$ osc start-build nodejs --follow
34+
$ oc start-build nodejs --follow
3535

36-
You can alternatively leave off `--follow` and use `osc build-logs nodejs-n` where n is the number of the build (output of start-build).
36+
You can alternatively leave off `--follow` and use `oc build-logs nodejs-n` where n is the number of the build (output of start-build).
3737

3838
#### deploy ####
3939

40-
happens automatically, to monitor its status either watch the web console or `osc get pods` to see when the pod is up. Another helpful command is
40+
happens automatically, to monitor its status either watch the web console or `oc get pods` to see when the pod is up. Another helpful command is
4141

42-
$ osc status
42+
$ oc status
4343

4444
This will help indicate what IP address the service is running, the default port for it to deploy at is 8080.
4545

0 commit comments

Comments
 (0)