You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ TLDR: OpenShift can generate and expose environment variables to your applicatio
27
27
###Development mode
28
28
When you develop your Rails application in OpenShift, you can also enable the 'development' environment by setting the RAILS_ENV environment variable for your deploymentConfiguration, using the `oc` client, like:
If you do so, OpenShift will run your application under 'development' mode. In development mode, your application will:
@@ -37,57 +37,57 @@ If you do so, OpenShift will run your application under 'development' mode. In d
37
37
Development environment can help you debug problems in your application in the same way as you do when developing on your local machine. However, we strongly advise you to not run your application in this mode in production.
38
38
39
39
###Installation:
40
-
These steps assume your OpenShift deployment has the default set of ImageStreams defined. Instructions for installing the default ImageStreams are available [here](http://docs.openshift.org/latest/admin_guide/install/first_steps.html)
40
+
These steps assume your OpenShift deployment has the default set of ImageStreams defined. Instructions for installing the default ImageStreams are available [here](http://docs.openshift.org/latest/admin_guide/install/first_steps.html). Instructions for installing the default ImageStreams are available [here](http://docs.openshift.org/latest/admin_guide/install/first_steps.html). If you are defining the set of ImageStreams now, remember to pass in the proper cluster-admin credentials and to create the ImageStreams in the 'openshift' namespace.
41
41
42
42
1. Fork a copy of [rails-ex](https://github.com/openshift/rails-ex)
43
43
2. Clone your repository to your development machine and cd to the repository directory
44
44
3. Add a Ruby application from the rails template:
4.Note that creating from a template will automatically start a new build. Watch your build progress:
48
+
4.Depending on the state of your system, and whether additional items need to be downloaded, it may take around a minute for your build to be started automatically. If you do not want to wait, run
49
49
50
-
$ oc build-logs rails-example-1
50
+
$ oc start-build rails-postgresql-example
51
51
52
-
5. Wait for frontend pods to start up (this can take a few minutes):
52
+
5. Once the build is running, watch your build progress
53
+
54
+
$ oc build-logs rails-postgresql-example-1
55
+
56
+
6. Wait for rails-postgresql-example pods to start up (this can take a few minutes):
In this case, the IP for frontend is 172.30.161.15 and it is on port 8080.
83
+
In this case, the IP for rails-postgresql-example rails-postgresql-example is 172.30.205.117 and it is on port 8080.
88
84
*Note*: you can also get this information from the web console.
89
85
90
86
87
+
###Debugging Unexpected Failures
88
+
89
+
Review some of the common tips and suggestions [here](https://github.com/openshift/origin/blob/master/docs/debugging-openshift.md).
90
+
91
91
###Adding Webhooks and Making Code Changes
92
92
Since OpenShift V3 does not provide a git repository out of the box, you can configure your github repository to make a webhook call whenever you push your code.
0 commit comments