generator-columbia-angular

generator-leviathan

Yeoman generator that scaffolds out a full stack Javascript web app using angularjs, Grunt and Bower, Node and Express, MongoDB and Redis.

Getting Started

Using this generator:

If you're not familiar with Yeoman and want to learn more If you want to build your own generator

Install Yeoman:

$ npm install -g yo

To install generator-columbia-angular from npm, run:

$ npm install -g generator-columbia-angular

Finally, initiate the generator:

$ yo columbia-angular optionalAppName

Before you actually can run the app, you need to make sure that mongodb is running. In a separate terminal run $ sudo mongod, then run $ grunt.

Recommended github and heroku setup:

run $ yo columbia-angular:deploy to setup both github and heroku automatically.

Note: If your version of git is out of date, heroku may refuse to create your app for the reasons specified at https://blog.heroku.com/archives/2014/12/24/update_your_git_clients_on_windows_and_os_x and you may have to first update git. If you choose to do this with homebrew, which I recommend (for making upgrading in the future easier), you may have to set your path to use /usr/local/bin/ before using /usr/bin/ (the default). You can do this by running:

$ brew sh

and should get the following message:

Your shell has been configured to use Homebrew's build environment:
this should help you build stuff. Notably though, the system versions of
gem and pip will ignore our configuration and insist on using the
environment they were built under (mostly). Sadly, scons will also
ignore our configuration.
When done, type `exit'.
brew \[\033[1;32m\]\w\[\033[0m\]$

Then restart your terminal. If that doesn't fix your issue, refer to this homebrew issue thread for additional workarounds:

The command uses the following to setup Github:

$ hub init
$ hub add . && hub commit -m "initial commit"
$ hub create optional_org_name/repo_name -d "description of repo"
$ hub push origin master

And to setup Heroku, it runs grunt build, copies over the Procfile, initializes the dist/ dir as a separate repository, and runs:

$ heroku apps:create herokuAppName && heroku config:set NODE_ENV=production
$ git add -A && git commit -m "Initial commit"
$ git push heroku master

all of which you can of course do at the command line, provided you have both hub and the heroku toolbelt installed.

More info on working with node in Heroku

The deploy generator also uses a plugin called heroku-config to push your local .env file to heroku. Install it with:

$ heroku plugins:install git://github.com/ddollar/heroku-config.git

Deployment requires that you have a remote mongo database to connect to. You can use heroku addons to create one:

 heroku addons:add mongolab

or you can [setup a mongolab account] and create one online. If you do this, just make sure to set the MONGOLAB_URI on heroku to the URI for accessing that db.

Versioning and releases

This project uses semantic versioning and github for releases. Releases can be created automatically using the grunt bump task, which will create a conventional changelog as well as a release. For more, see:

grunt-release github on creating releases grunt-conventional-changelog commit conventions node-semver

To create new releases with changelogs using the autorelease as it currently stands:

1. $ grunt bump:releaseType
2. $ grunt autorelease:releaseType

Release type should be one of patch, minor, major, or prerelease

running grunt bump simply bumps the version, which enables conventional changelog to use the correct latest version when generating its changelog. grunt autorelease then does the following:

1. runs the "changelog" task

• Generates changelog from previous version to HEAD...
• Parses commits since last version
• updates CHANGELOG.md updated

1. runs the "addchangelog" task:

• stages CHANGELOG.md
• committs CHANGELOG.md

1. runs the "release:patch" (release) task:

• stages package.json
• commits package.json
• creates new git tag: v0.2.8
• pushes to remote git repo
• pushes new tag 0.2.8 to remote git repo

To then test the production version: $ grunt build $ grunt serve:prod

To then commit and push the production version to heroku: $ cd dist $ git status $ git add --all

And normally we include a message like: $ git commit -m "feat(v0.2.3): dist build for v0.2.3" $ git push heroku master

Inspirations:

• Originally forked from leviathantech/generator-leviathan
• Codebase inspired by and originally based off of DaftMonk/generator-angular-fullstack

Publishing to npm

Go to https://www.npmjs.com/ and click on "create account". You must have an account on npm in order to publish modules

Before publishing

1. Test the version locally by: a. linking the module to npm by running $ npm link inside the repo root b. linking to the linked module by running $ npm link <module-name> from inside the directory you wish to use it in.
2. Once you're ready to publish, run $ npm unlink inside repo root and $npm unlink <module-name> inside test dir so you don't still have the local version linked in.
3. if this is the first time publishing run $ npm publish.
4. Otherwise, you must bump the version before running this command. This should be done using the grunt bump and grunt autorelease commands specified above (eventually this should also publish to npm automatically).

Changelog

1.1.2 (2015-02-07)

Bug Fixes

• index.js:
  • yeoman logger doesn't seem to be available in deploy child process, so log to co (700051db)
  • install npm and then bower to get correct messages for bower conflicts (9a2ec76b)
• injector.js: add in file checks to prevent injecting tests into index.html, which then get ug (1ce74df2)
• lvAuthWidget.spec.js: modify test for displayLogin so all tests pass, closes #16 (eb44fa4f)
• lvUserService.spec.js: rename improperly named spec file, closes #26 (ba11a914)
• nav-menu.html: fix broken nav dropdown with new require attributes from angular-bootstrap, fixe (ec1a14b3)
• package.json: fix repository info so that the url enables conventional changelog to generate t (c1e1a07e)
• style.scss: use protocol-related url (by not specifying http) so it can be loaded in secure (d7f72ff6)

Features

• _package.json: use organizationname for github url, update repo description, closes #13 (393d9f1c)
• externalServicesPrompts.js: add organizationname (github username or organization) to prompts (e82b6833)

<a name="1.1.1"></a>