Generate forms-angular applications for the MEAN stack
npm install generator-fngYeoman generator for creating forms-angular applications, using the MEAN stack of MongoDB, Express, AngularJS, and Node.
Install generator-fng:
``
npm install -g generator-fng
Make a new directory, and cd into it:`
mkdir my-new-project && cd $_
Run yo fng, optionally passing an app name:`
yo fng [app-name]
Run grunt for building, grunt serve for preview, and grunt serve:dist for a preview of the built app.
* See the Prepare section of http://www.forms-angular.org/#!/get-started#prepare
Client
* Scripts: JavaScript
* Markup:
* Stylesheets:
* Angular Routers: , ui-router
Server
* Database: MongoDB
* Authentication boilerplate: , No
* oAuth integrations: Twitter Google
* Socket.io integration: , No
A grunt task looks for new files in your client/app and client/components folder and automatically injects them in the appropriate places based on an injection block.
* css files into client/index.html
* files into client/index.html
Available generators:
* App
- fng (aka fng:app)
* Server Side
- fng:endpoint
* Client Side
- fng:route
- fng:controller
- fng:filter
- fng:directive
- fng:service
- fng:provider
- fng:factory
- fng:decorator
* Deployment
- fng:openshift
- fng:heroku
Example:
`bash`
yo fng
Example:
`bash`
yo fng:endpoint message
[?] What will the url of your endpoint be? /api/messages
Produces:
server/api/message/index.js
server/api/message/message.spec.js
server/api/message/message.controller.js
server/api/message/message.model.js (optional)
server/api/message/message.socket.js (optional)
Example:
`bash`
yo fng:route myroute
[?] Where would you like to create this route? client/app/
[?] What will the url of your route be? /myroute
Produces:
client/app/myroute/myroute.js
client/app/myroute/myroute.controller.js
client/app/myroute/myroute.controller.spec.js
client/app/myroute/myroute.html
client/app/myroute/myroute.scss
Example:
`bash`
yo fng:controller user
[?] Where would you like to create this controller? client/app/
Produces:
client/app/user/user.controller.js
client/app/user/user.controller.spec.js
Example:
`bash`
yo fng:directive myDirective
[?] Where would you like to create this directive? client/app/
[?] Does this directive need an external html file? Yes
Produces:
client/app/myDirective/myDirective.directive.js
client/app/myDirective/myDirective.directive.spec.js
client/app/myDirective/myDirective.html
client/app/myDirective/myDirective.scss
Simple directive without an html file
Example:
`bash`
yo fng:directive simple
[?] Where would you like to create this directive? client/app/
[?] Does this directive need an external html file? No
Produces:
client/app/simple/simple.directive.js
client/app/simple/simple.directive.spec.js
Example:
`bash`
yo fng:filter myFilter
[?] Where would you like to create this filter? client/app/
Produces:
client/app/myFilter/myFilter.filter.js
client/app/myFilter/myFilter.filter.spec.js
Example:
`bash`
yo fng:service myService
[?] Where would you like to create this service? client/app/
Produces:
client/app/myService/myService.service.js
client/app/myService/myService.service.spec.js
You can also do yo angular-fullstack:factory and yo angular-fullstack:provider for other types of services.
Example:
`bash`
yo fng:decorator serviceName
[?] Where would you like to create this decorator? client/app/
Produces
client/app/serviceName/serviceName.decorator.js
###Openshift
Deploying to OpenShift can be done in just a few steps:
yo fng:openshift
A live application URL will be available in the output.
> oAuth
>
> 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 :
>
> rhc set-env FACEBOOK_ID=id -a my-openshift-app
> rhc set-env FACEBOOK_SECRET=secret -a my-openshift-app
>
> You will also need to set DOMAIN environment variable:
>
> rhc config:set DOMAIN=
>
> # or (if you're using it):
>
> rhc config:set DOMAIN=
>
> After you've set the required environment variables, restart the server:
>
> rhc app-restart -a my-openshift-app
To make your deployment process easier consider using grunt-build-control.
Pushing Updates
grunt
Commit and push the resulting build, located in your dist folder:
grunt buildcontrol:openshift
Deploying to heroku only takes a few steps.
yo fng:heroku
To work with your new heroku app using the command line, you will need to run any heroku commands from the dist folder.
If you're using mongoDB you will need to add a database to your app:
heroku addons:add mongolab
Your app should now be live. To view it run heroku open.
>
> 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 :
>
> heroku config:set FACEBOOK_ID=id
> heroku config:set FACEBOOK_SECRET=secret
>
> You will also need to set DOMAIN environment variable:
>
> heroku config:set DOMAIN=
>
> # or (if you're using it):
>
> heroku config:set DOMAIN=
>
To make your deployment process easier consider using grunt-build-control.
#### Pushing Updates
grunt
Commit and push the resulting build, located in your dist folder:
grunt buildcontrol:heroku
The following packages are always installed by the app generator:
* angular
* angular-cookies
* angular-mocks
* angular-resource
* angular-sanitize
* angular-scenario
* es5-shim
* font-awesome
* json3
* jquery
* lodash
These packages are installed optionally depending on your configuration:
* angular-route
* angular-ui-router
* angular-socket-io
* angular-bootstrap
* bootstrap
All of these can be updated with bower update as new versions are released.
A .yo-rc file is generated for helping you copy configuration across projects, and to allow you to keep track of your settings. You can change this as you see fit.
Running grunt test will run the client and server unit tests with karma and mocha.
Use grunt test:server to only run server tests.
Use grunt test:client to only run client tests.
Protractor tests
To setup protractor e2e tests, you must first run
npm run update-webdriver
Use grunt test:e2e to have protractor go through tests located in the e2e folder.
Keeping your app secrets and other sensitive information in source control isn't a good idea. To have grunt launch your app with specific environment variables, add them to the git ignored environment config file: server/config/local.env.js.
Overview
├── client
│ ├── app - All of our app specific components go in here
│ ├── assets - Custom assets: fonts, images, etc…
│ ├── components - Our reusable components, non-specific to to our app
│
├── e2e - Our protractor end to end tests
│
└── server
├── api - Our apps server api
├── auth - For handling authentication with different auth strategies
├── components - Our reusable or app-wide components
├── config - Where we do the bulk of our apps configuration
│ └── local.env.js - Keep our environment variables out of source control
│ └── environment - Configuration specific to the node environment
└── views - Server rendered views
An example client component in client/app
main
├── main.js - Routes
├── main.controller.js - Controller for our main route
├── main.controller.spec.js - Test
├── main.html - View
└── main.less - Styles
An example server component in server/api
thing
├── index.js - Routes
├── thing.controller.js - Controller for our thing endpoint
├── thing.model.js - Database model
├── thing.socket.js - Register socket events
└── thing.spec.js - Test
See the contributing docs
This project has 2 main branches: master and canary. The master branch is where the current stable code lives and should be used for production setups. The canary branch is the main development branch, this is where PRs should be submitted to (backport fixes may be applied to master).
By seperating the current stable code from the cutting-edge development we hope to provide a stable and efficient workflow for users and developers alike.
When submitting an issue, please follow the guidelines. Especially important is to make sure Yeoman is up-to-date, and providing the command or commands that cause the issue.
When submitting a PR, make sure that the commit messages match the AngularJS conventions.
When submitting a bugfix, try to write a test that exposes the bug and fails before applying your fix. Submit the test alongside the fix.
When submitting a new feature, add tests that cover the feature.
See the travis.yml` for configuration required to run tests.