Skip to content

Commit d73b573

Browse files
committed
feat(gen:cloudfoundry): update readme
1 parent b96da3f commit d73b573

File tree

1 file changed

+32
-1
lines changed

1 file changed

+32
-1
lines changed

Diff for: readme.md

+32-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# AngularJS Full-Stack generator [![Build Status](https://travis-ci.org/DaftMonk/generator-angular-fullstack.svg?branch=master)](http://travis-ci.org/DaftMonk/generator-angular-fullstack) [![Gitter chat](https://badges.gitter.im/gitterHQ/gitter.png)](https://gitter.im/DaftMonk/generator-angular-fullstack)
1+
# AngularJS Full-Stack generator [![Build Status](https://travis-ci.org/DaftMonk/generator-angular-fullstack.svg?branch=master)](http://travis-ci.org/DaftMonk/generator-angular-fullstack)
22

33
> Yeoman generator for creating MEAN stack applications, using MongoDB, Express, AngularJS, and Node - lets you quickly set up a project following best practices.
44
@@ -78,6 +78,7 @@ Available generators:
7878
* Deployment
7979
- [angular-fullstack:openshift](#openshift)
8080
- [angular-fullstack:heroku](#heroku)
81+
- [angular-fullstack:cloudfoundry](#cloudfoundry)
8182

8283
### App
8384
Sets up a new AngularJS + Express app, generating all the boilerplate you need to get started.
@@ -291,6 +292,36 @@ Commit and push the resulting build, located in your dist folder:
291292
grunt buildcontrol:heroku
292293

293294

295+
### Cloud Foundry / Pivotal Web Services
296+
297+
Deploying to Cloud Foundry can be done with these steps.
298+
299+
yo angular-fullstack:cloudfoundry
300+
301+
To work with your new Cloud Foundry app using the command line, you will need to run any `cf` commands from the `dist` folder.
302+
303+
304+
If you're using mongoDB you will need to create a service (MongoLab) and bind it to your app:
305+
306+
cf create-service mongolab sandbox my-mongo
307+
cf bind-service my-app my-mongo
308+
309+
>
310+
> 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 :
311+
>
312+
> cf set-env my-app FACEBOOK_ID id
313+
> cf set-env my-app FACEBOOK_SECRET secret
314+
>
315+
316+
#### Pushing Updates
317+
318+
grunt
319+
320+
Deploy the resulting build, from your `dist` folder:
321+
322+
cf push
323+
324+
294325
## Bower Components
295326

296327
The following packages are always installed by the [app](#app) generator:

0 commit comments

Comments
 (0)