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
[?] Where would you like to create this directive? client/app/
217
-
[?] Does this directive need an external html file? No
218
-
```
219
-
220
-
Produces:
221
-
222
-
client/app/simple/simple.directive.js
223
-
client/app/simple/simple.directive.spec.js
224
-
225
-
### Filter
226
-
Generates a filter.
227
-
228
-
Example:
229
-
```bash
230
-
yo angular-fullstack:filter myFilter
231
-
[?] Where would you like to create this filter? client/app/
232
-
```
233
-
234
-
Produces:
235
-
236
-
client/app/myFilter/myFilter.filter.js
237
-
client/app/myFilter/myFilter.filter.spec.js
238
-
239
-
### Service
240
-
Generates an AngularJS service.
241
-
242
-
Example:
243
-
```bash
244
-
yo angular-fullstack:service myService
245
-
[?] Where would you like to create this service? client/app/
246
-
```
247
-
248
-
Produces:
249
-
250
-
client/app/myService/myService.service.js
251
-
client/app/myService/myService.service.spec.js
252
-
253
-
254
-
You can also do `yo angular-fullstack:factory` and `yo angular-fullstack:provider` for other types of services.
255
-
256
-
### Decorator
257
-
Generates an AngularJS service decorator.
258
-
259
-
Example:
260
-
```bash
261
-
yo angular-fullstack:decorator serviceName
262
-
[?] Where would you like to create this decorator? client/app/
263
-
```
264
-
265
-
Produces
266
-
267
-
client/app/serviceName/serviceName.decorator.js
268
-
269
-
###Openshift
270
-
271
-
> 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/).
272
-
273
-
Deploying to OpenShift can be done in just a few steps:
274
-
275
-
yo angular-fullstack:openshift
276
-
277
-
A live application URL will be available in the output.
278
-
279
-
> **oAuth**
280
-
>
281
-
> 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 :
282
-
>
283
-
> rhc set-env FACEBOOK_ID=id -a my-openshift-app
284
-
> rhc set-env FACEBOOK_SECRET=secret -a my-openshift-app
285
-
>
286
-
> You will also need to set `DOMAIN` environment variable:
> After you've set the required environment variables, restart the server:
295
-
>
296
-
> rhc app-restart -a my-openshift-app
297
-
298
-
To make your deployment process easier consider using [grunt-build-control](https://github.com/robwierzbowski/grunt-build-control).
299
-
300
-
**Pushing Updates**
301
-
302
-
grunt
303
-
304
-
Commit and push the resulting build, located in your dist folder:
305
-
306
-
grunt buildcontrol:openshift
307
-
308
-
### Heroku
309
-
310
-
Deploying to heroku only takes a few steps.
311
-
312
-
yo angular-fullstack:heroku
313
-
314
-
To work with your new heroku app using the command line, you will need to run any `heroku` commands from the `dist` folder.
315
-
316
-
317
-
If you're using mongoDB you will need to add a database to your app:
318
-
319
-
heroku addons:create mongolab
320
-
321
-
Note: if you get an `Error: No valid replicaset instance servers found` you need to modify moongose connection options in config/environment/production.js as follows:
One of the odd things about the Node driver is that the default timeout for replica set connections is only 1 second, so make sure you're setting it to something more like 30s like in this example.
332
-
333
-
334
-
Your app should now be live. To view it run `heroku open`.
335
-
336
-
>
337
-
> 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 :
338
-
>
339
-
> heroku config:set FACEBOOK_ID=id
340
-
> heroku config:set FACEBOOK_SECRET=secret
341
-
>
342
-
> You will also need to set `DOMAIN` environment variable:
0 commit comments