<commit_before># Vagrant::Notify

[![Build Status](https://travis-ci.org/fgrehm/vagrant-notify.png)](https://travis-ci.org/fgrehm/vagrant-notify)
[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/fgrehm/vagrant-notify)

A Vagrant plugin that forwards `notify-send` from guest to host machine, tested
using Ubuntu as guest and host machine.

## Installation

Make sure you have Vagrant >= 1.1 around and run:

```terminal
$ vagrant plugin install vagrant-notify
```



## Usage

After installing the gem, whenever you run `vagrant up`, a Ruby
[TCPServer](http://www.ruby-doc.org/stdlib-1.9.3/libdoc/socket/rdoc/TCPServer.html)
will fire up on `8081` port and a [script](https://github.com/fgrehm/vagrant-notify/blob/master/files/notify-send.erb)
will be installed on the guest machine to replace the original `notify-send`
command.

If by any chance your IP changes, you can run `vagrant provision` in order to
update the guest script with the new IP.

As of now, the plugin is not supported on multi vm environments, it used to be
for the Vagrant < 1.1 version and I'm planning to fix that as soon as I have a chance.


## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request<commit_msg>Add known issues section to readme<commit_after># Vagrant::Notify

[![Build Status](https://travis-ci.org/fgrehm/vagrant-notify.png)](https://travis-ci.org/fgrehm/vagrant-notify)
[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/fgrehm/vagrant-notify)

A Vagrant plugin that forwards `notify-send` from guest to host machine, tested
using Ubuntu as guest and host machine.

## Installation

Make sure you have Vagrant >= 1.1 around and run:

```terminal
$ vagrant plugin install vagrant-notify
```



## Usage

After installing the gem, whenever you run `vagrant up`, a Ruby
[TCPServer](http://www.ruby-doc.org/stdlib-1.9.3/libdoc/socket/rdoc/TCPServer.html)
will fire up on `8081` port and a [script](https://github.com/fgrehm/vagrant-notify/blob/master/files/notify-send.erb)
will be installed on the guest machine to replace the original `notify-send`
command.

If by any chance your IP changes, you can run `vagrant provision` in order to
update the guest script with the new IP.

## Known issues

* Does not work properly on multi vm environments, it used to work on a Vagrant
  < 1.1 version and I'm planning to fix that as soon as I have a chance.

* vagrant's `suspend` does not stop the notification server


## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
{'fraction_non_alphanumeric': 0.11203319502074689, 'fraction_numerical': 0.011065006915629323, 'mean_word_length': 4.327808471454881, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 10, 'lorem ipsum': 0, 'www.': 2, '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': '4241600', 'n_tokens_mistral': 958, 'n_tokens_neox': 912, 'n_words': 348}