Skip to content

Commit 5f1bf13

Browse files
committed
docs(generators:openshift): create openshift.md
[skip ci]
1 parent 2fe295e commit 5f1bf13

File tree

1 file changed

+38
-0
lines changed

1 file changed

+38
-0
lines changed

docs/generators/openshift.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
###Openshift
2+
3+
> Note: Openshift uses a quite old version of Node by default. We strongly recommend updating your Node version. [Here's a helpful article](https://blog.openshift.com/any-version-of-nodejs-you-want-in-the-cloud-openshift-does-it-paas-style/).
4+
5+
Deploying to OpenShift can be done in just a few steps:
6+
7+
yo angular-fullstack:openshift
8+
9+
A live application URL will be available in the output.
10+
11+
> **oAuth**
12+
>
13+
> If you're using any oAuth strategies, you must set environment variables for your selected oAuth. For example, if we're using Facebook oAuth we would do this :
14+
>
15+
> rhc set-env FACEBOOK_ID=id -a my-openshift-app
16+
> rhc set-env FACEBOOK_SECRET=secret -a my-openshift-app
17+
>
18+
> You will also need to set `DOMAIN` environment variable:
19+
>
20+
> rhc set-env DOMAIN=<your-openshift-app-name>.rhcloud.com
21+
>
22+
> # or (if you're using it):
23+
>
24+
> rhc set-env DOMAIN=<your-custom-domain>
25+
>
26+
> After you've set the required environment variables, restart the server:
27+
>
28+
> rhc app-restart -a my-openshift-app
29+
30+
To make your deployment process easier consider using [grunt-build-control](https://github.com/robwierzbowski/grunt-build-control).
31+
32+
**Pushing Updates**
33+
34+
grunt
35+
36+
Commit and push the resulting build, located in your dist folder:
37+
38+
grunt buildcontrol:openshift

0 commit comments

Comments
 (0)