<commit_before>#AngularJS boilerplate (study) [![Build Status](https://travis-ci.org/dandaniel/angular-boilerplate-study.svg?branch=master)](https://travis-ci.org/dandaniel/angular-boilerplate-study)

This study looks at AngularJS boilerplates to find the best approaches so you don't have to. Although plenty of choices are available, they will do justice for only some types of applications. There is no one-size-fits all, universal boilerplate.
Plan your app well, prototype it and then refactor. If you still think it's a good idea to use a boilerplate, choose one and adapt it to your needs.

[See this app in action](http://abs.danmind.ru).


##Getting started

Install `npm` and `bower` dependencies and run `grunt`, that's it. You are good to go.

```
$ sudo npm install
$ bower install
$ grunt
```

After running grunt, the source files will be built into `./build`.
Navigate to the build directory and start a server (recommended port is 8008) in order to see the app in action.

```sh
# For the lazy developer, just run the following to start the build server
# and open a new tab in your favorite browser:

$ grunt dev
```

When the app is ready for production, compile the app into `./application` by running:

```
$ grunt compile
```

```sh
# Same as with build, run the following to start the production server
# and open a new tab in your favorite browser:

$ grunt prod
```


##Table of contents

  1. [Intro](#intro)
  2. [Philosophy](#philosophy)
  3. [Application structure](#application-structure)
  4. [Build and compile](#build-and-compile)
    * [Build](#build)
    * [Compile](#compile)
  5. [Core components](#core-components)
  6. [Third party components](#third-party-components)
  7. [Conventions and best practices](#conventions-and-best-practices)
  8. [Testing](#testing)
    * [Unit testing](#unit)
    * [End to end testing](#end-to-end)
<commit_msg>removed redundant info on how to start dev/prod server<commit_after>#AngularJS boilerplate (study) [![Build Status](https://travis-ci.org/dandaniel/angular-boilerplate-study.svg?branch=master)](https://travis-ci.org/dandaniel/angular-boilerplate-study)

This study looks at AngularJS boilerplates to find the best approaches so you don't have to. Although plenty of choices are available, they will do justice for only some types of applications. There is no one-size-fits all, universal boilerplate.
Plan your app well, prototype it and then refactor. If you still think it's a good idea to use a boilerplate, choose one and adapt it to your needs.

[See this app in action](http://abs.danmind.ru).


##Getting started

Install `npm` and `bower` dependencies and run `grunt`, that's it. You are good to go.

```
$ sudo npm install
$ bower install
$ grunt
```

After running grunt, the source files will be built into `./build`.

When the app is ready for production, compile the app into `./application` by running:

```
$ grunt compile
```


##Table of contents

  1. [Intro](#intro)
  2. [Philosophy](#philosophy)
  3. [Application structure](#application-structure)
  4. [Build and compile](#build-and-compile)
    * [Build](#build)
    * [Compile](#compile)
  5. [Core components](#core-components)
  6. [Third party components](#third-party-components)
  7. [Conventions and best practices](#conventions-and-best-practices)
  8. [Testing](#testing)
    * [Unit testing](#unit)
    * [End to end testing](#end-to-end)

{'fraction_non_alphanumeric': 0.11564426181391253, 'fraction_numerical': 0.0058702670971529205, 'mean_word_length': 4.300155520995334, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6971712', 'n_tokens_mistral': 1094, 'n_tokens_neox': 996, 'n_words': 406}