<commit_before># Matador

A node-based web interface for the <a href="https://github.com/OptimalBits/bull">Bull Job Manager</a>
***

**Update Note version 0.1.0 -> 1.0.0**  
In the latest update, Matador went from relying on Kraken to relying on just express/dust (which is why I incremented by a major version number). This occurred because Kraken has changed quite a bit since Matador was made, with quite a bit of the previous code becoming deprecated. I also re-worked some of the code to try to make it quicker and resolve some of the issues/feature requests.

**Why?**  
We needed a job manager and we wanted to stick to one that only really relied on Node and Redis, so we looked and looked until we found Bull. Bull looked really nice, but we also wanted to be able to monitor the jobs without having to actually log into the AWS server to access the Redis database. Thus, Matador was born.

**Why not just use Kue?**  
Kue has some <a href="https://github.com/LearnBoost/kue/issues/53">really old</a>, <a href="https://github.com/LearnBoost/kue/issues/130">outstanding bugs</a> that we encounted just while testing it. We tested Bull quite a bit, and couldn't reproduce these bugs. We thought it'd be easier to build an interface for Bull than to use Kue and deal with those bugs. (Notice that the first one, while closed, was never actually fixed...)

##Getting Started##

###Installing###

Easy! If you're using Bull already, then all you need to do is clone this repo and run

`npm install`

###Running###

You can run the app standalone with

`node index.js`  or  `npm start`

This standalone method will require you to modify the config/development.json and config/production.json files so that it has the right values for your host and port for your redis server (also any additional redis options, such as passwords).

Or you can simply
```js
var app = require('matador/app')(options);
app.listen(1337);

// http://localhost:1337/
```

Where options is completely optional.  If not specified, it will default to the development settings in config.
You can also pass in your own redis configuration thusly:

```js
var matador = require('matador/app')({
  redis: {
    host: your host name,
    port: your port number,
    password: <PASSWORD>
  }
});
```
<commit_msg>Updated npm part with correct npm name 'bull-ui'<commit_after># Matador

A node-based web interface for the <a href="https://github.com/OptimalBits/bull">Bull Job Manager</a>
***

**Update Note version 0.1.0 -> 1.0.0**  
In the latest update, Matador went from relying on Kraken to relying on just express/dust (which is why I incremented by a major version number). This occurred because Kraken has changed quite a bit since Matador was made, with quite a bit of the previous code becoming deprecated. I also re-worked some of the code to try to make it quicker and resolve some of the issues/feature requests.

**Why?**  
We needed a job manager and we wanted to stick to one that only really relied on Node and Redis, so we looked and looked until we found Bull. Bull looked really nice, but we also wanted to be able to monitor the jobs without having to actually log into the AWS server to access the Redis database. Thus, Matador was born.

**Why not just use Kue?**  
Kue has some <a href="https://github.com/LearnBoost/kue/issues/53">really old</a>, <a href="https://github.com/LearnBoost/kue/issues/130">outstanding bugs</a> that we encounted just while testing it. We tested Bull quite a bit, and couldn't reproduce these bugs. We thought it'd be easier to build an interface for Bull than to use Kue and deal with those bugs. (Notice that the first one, while closed, was never actually fixed...)

##Getting Started##

###Installing###

Easy! If you're using Bull already, then all you need to do is clone this repo and run

`npm install`

###Running standalone from npm###

You can run the app standalone with

`node index.js`  or  `npm start`

This standalone method will require you to modify the config/development.json and config/production.json files so that it has the right values for your host and port for your redis server (also any additional redis options, such as passwords).

Or you can simply

`npm install bull-ui`

```js
  var app = require('bull-ui/app')(options);
  app.listen(1337, function(){
    console.log('bull-ui started listening on port', this.address().port);
  });

// http://localhost:1337/
```

Where options is completely optional.  If not specified, it will default to the development settings in config.
You can also pass in your own redis configuration thusly:

```js
var matador = require('matador/app')({
  redis: {
    host: your host name,
    port: your port number,
    password: <PASSWORD>
  }
});
```

{'fraction_non_alphanumeric': 0.08736020257438278, 'fraction_numerical': 0.008018569318421608, 'mean_word_length': 4.080385852090032, 'pattern_counts': {'":': 0, '<': 17, '<?xml version=': 0, '>': 19, 'https://': 6, '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': '6825078', 'n_tokens_mistral': 1377, 'n_tokens_neox': 1290, 'n_words': 692}